UNSOLVED

segapeli

updated

17 years ago

S

segapeli

1 Rookie

8 Posts

0

3858

January 22nd, 2010 12:00

SDK reports error=-10101

Hi,

I am seeing the SOCKET Error ( -10101) from an SDK trace during a write operation.  I know this could mean all sorts of network issues, however I only see this when the SDK is used on an HP/UX system . When the SDK is used from an AIX or Windows system within the same environment (same data and network ) the store operations work fine.  The SDK trace however shows that the SDK that appears to stall for exactly two minutes. See the timestamps in the trace below:

1263418646181    2010-01-13 21:37:26.181        [debug]        6275.77    [TRANSACTION]    Export Data albert/125/WRITE_BLOB
1263418646181    2010-01-13 21:37:26.181        [debug]        6275.77    [PACKET]    send SmartPacket
  NET_SYSTEMID type=string value=albert
  NET_TRANSACTIONID type=string value=albert/125/WRITE_BLOB
  NET_VERSION type=integer value=3  HPP_CLIENT_VERSION type=integer value=197124  NET_MESSAGEID type=integer value=42  HPP_VERSION type=integer value=1  HPP_CONTROL type=integer value=0  HPP_OFFSET type=long value=1441792  HPP_SEGDATA type=bytearray value=16384

1263418766190    2010-01-13 21:39:26.190        [debug]        6275.77    [EXCEPTION]    In 'Connection.cpp' at line 556: Exception
error=-10101
syserror=0
message=send: waitForWritingData(120000) returned zero
trace=No trace available

The SDK API Reference states that the default timeout for idle connections is two minutes so I am assuming that this socket error is simply a connection time out.  But what is the SDK doing in between these two trace statements for two minutes?

The error is intermittent.

Thanks.