Orbacus requests overlapping in multithread client

0 Likes

Summary
Article Number 24859
Environment Orbacus 4.3.3 on Windows
Question/Problem Description Multithread Orbacus clients may seen COMM_FAILURE exceptions with a WSAECONNRESET reason. 
Clarifying Information
Error Message System exception `COMM_FAILURE' Reason: error number WSAECONNRESET
Defect/Enhancement Number OB-92
Cause This is due to two threads writing to the same connection in an unsafe manner leading to garbage being sent to the server.
Resolution Fixed in the latest patch to Orbacus 4.3.4
Workaround Increase the TCP window size at both server and client, to increase the packet length. This will decrease the likelyhood of the error occurring.
 
Notes
Attachment

Created date: 23 September 2011
Last Modified: 13 February 2013
Last Published: 12 May 2012
First Published date: 03 October 2011
Comment List
Anonymous
Related Discussions
Recommended