TCPIP Connection Drop Issue

, , , , , ,
1

In our shop we have connx jdbc running on windows server and the connx listener running on z/os. Periodically we see tcicp connection - socket 10054 error in the jdbc log:

Dec 18 12:26:18.706 2012@LM_INFO @ UPTIME:(00 00:00:01.625 ) IP:(172.24.59.15 ) TID:(1644 )==> 2009(W): Thread starting: 1644.
Dec 18 12:26:18.722 2012@LM_DEBUG @ UPTIME:(00 00:00:01.641 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (DriverConnect).
Dec 18 12:26:18.722 2012@LM_INFO @ UPTIME:(00 00:00:01.641 ) IP:(172.24.59.15 ) TID:(1644 )==> 2019(W): Connecting to DSN: (EPIC_Integration).
Dec 18 12:26:23.582 2012@LM_DEBUG @ UPTIME:(00 00:00:06.501 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (ConnectionGetInfo).
Dec 18 12:26:23.597 2012@LM_DEBUG @ UPTIME:(00 00:00:06.516 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (StatementCreate).
Dec 18 12:26:23.613 2012@LM_DEBUG @ UPTIME:(00 00:00:06.532 ) IP:(172.24.59.15 ) TID:(1644 )==> 2012(W): SQL: select * from table_col {maxrows 1}.
Dec 18 12:26:23.628 2012@LM_DEBUG @ UPTIME:(00 00:00:06.547 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (StatementCmd).
Dec 18 12:26:23.628 2012@LM_DEBUG @ UPTIME:(00 00:00:06.547 ) IP:(172.24.59.15 ) TID:(1644 )==>Command Type is EXECUTE(5)
Dec 18 12:26:23.628 2012@LM_DEBUG @ UPTIME:(00 00:00:06.547 ) IP:(172.24.59.15 ) TID:(1644 )==> 2013(W): Begin Executing Query.
Dec 18 12:26:23.644 2012@LM_DEBUG @ UPTIME:(00 00:00:06.563 ) IP:(172.24.59.15 ) TID:(1644 )==> 2014(W): Query Execution Complete
Dec 18 12:26:23.675 2012@LM_DEBUG @ UPTIME:(00 00:00:06.594 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (StatementCmd).
Dec 18 12:26:23.675 2012@LM_DEBUG @ UPTIME:(00 00:00:06.594 ) IP:(172.24.59.15 ) TID:(1644 )==>Command Type is CLOSESTATEMENT(4)
Dec 18 12:56:33.690 2012@LM_DEBUG @ UPTIME:(00 00:30:16.609 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (StatementCmd).
Dec 18 12:56:33.690 2012@LM_DEBUG @ UPTIME:(00 00:30:16.609 ) IP:(172.24.59.15 ) TID:(1644 )==>Command Type is EXECUTE(5)
Dec 18 12:56:33.690 2012@LM_DEBUG @ UPTIME:(00 00:30:16.609 ) IP:(172.24.59.15 ) TID:(1644 )==> 2013(W): Begin Executing Query.
Dec 18 12:57:30.489 2012@LM_DEBUG @ UPTIME:(00 00:31:13.408 ) IP:(172.24.59.15 ) TID:(1644 )==> 2014(W): Query Execution Complete
Dec 18 12:57:30.489 2012@LM_ERROR @ UPTIME:(00 00:31:13.408 ) IP:(172.24.59.15 ) TID:(1644 )==> 2007(W): Warning: Error messages to follow:
Dec 18 12:57:30.489 2012@LM_ERROR @ UPTIME:(00 00:31:13.408 ) IP:(172.24.59.15 ) TID:(1644 )==> 2010(E): (HY000): Unable to send message to server.GetMessage :ReadMessage - failed -1 :TCPIP :ReadMessage Failure. SocketError(10054)

.
Dec 18 12:57:30.504 2012@LM_DEBUG @ UPTIME:(00 00:31:13.423 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (StatementCmd).
Dec 18 12:57:30.504 2012@LM_DEBUG @ UPTIME:(00 00:31:13.423 ) IP:(172.24.59.15 ) TID:(1644 )==>Command Type is DROPSTATEMENT(8)
Dec 18 12:57:30.520 2012@LM_DEBUG @ UPTIME:(00 00:31:13.439 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (ConnectionGetWarnings).
Dec 18 12:57:30.551 2012@LM_DEBUG @ UPTIME:(00 00:31:13.470 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (ConnectionCmd).
Dec 18 12:57:30.551 2012@LM_ERROR @ UPTIME:(00 00:31:13.470 ) IP:(172.24.59.15 ) TID:(1644 )==> 2007(W): Warning: Error messages to follow:
Dec 18 12:57:30.551 2012@LM_ERROR @ UPTIME:(00 00:31:13.470 ) IP:(172.24.59.15 ) TID:(1644 )==> 2010(E): (HY000): Unable to send message to server.SendMessage :Socket is null
.
Dec 18 12:57:30.567 2012@LM_DEBUG @ UPTIME:(00 00:31:13.486 ) IP:(172.24.59.15 ) TID:(1644 )==> 2018(W): Processing CDO: (ConnectionCmd).
Dec 18 12:57:30.567 2012@LM_INFO @ UPTIME:(00 00:31:13.486 ) IP:(172.24.59.15 ) TID:(1644 )==> 2008(W): Client close message.
Dec 18 12:57:30.567 2012@LM_INFO @ UPTIME:(00 00:31:13.486 ) IP:(172.24.59.15 ) TID:(1644 )==> 2010(W): Thread completed: 1644.

For the CONNX CONNECTTIMEOUT parameter we take on the default of 30sec. Is the socket 10054 happened because the query took > 1 min to execute? Just want to validate my thoughts.

Any disadvantage with increasing the CONNECTTIMEOUT parameter?

Thanks.

2

The log indicates that the error did not occur during the connection but after the connection was established and during the execution of a query. I would recommend you report this error through support channels for further analysis.