Connection problem.

[jolu...@hotmail.com]

Hi guys,<br />
<br />
I have been having problems with my WASND 6.0 environments which is causing transaction timeouts, a lot of hanging threads and eventually bringin the environments down.<br />
<br />
From my research into error codes 'DSRA0080E', 'DSRA00010E' &#38; 'SQL STATE 57030' which frequently occur in the SystemOut.log, it seems the issue is either database or network. However, there seems to be nothing wrong with either.<br />
<br />
Any advise please?<br />
<br />
++--12/6/07 5:21:00:221 GMT-- 00000173 WSRdbManagedC W DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: com.ibm.db2.jcc.a.SqlException: invalid operation: connection closed++<br />
++at com.ibm.db2.jcc.a.p.Hb(p.java(Compiled Code))++<br />
++at com.ibm.db2.jcc.a.p.getAutoCommit(p.java:1147)++<br />
<br />
++.....++<br />
<br />
++.++<br />
++--12/6/07 5:21:01:125 GMT-- 00000173 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jdbc/db2Connection. The exception which was received is com.ibm.websphere.ce.cm.StaleConnectionException: A communication error has been detected. Communication protocol being used: T4Agent.sendRequest(). Communication API being used: OutputStream.flush(). Location where the error was detected: There is no process to read data written to a pipe.. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: C0A80899.F3CA.071205230802++<br />
++--12/6/07 5:21:01:863 GMT-- 00000173 MCWrapper E J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection WSRdbManagedConnectionImpl@60cf0658 from resource No longer available. Caught exception: com.ibm.ws.exception.WsException: DSRA1130E: A fatal connection error occurred on another connection while this connection was active. This connection cannot be reset to a usable state.++<br />
++at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.&lt;init&gt;(DataStoreAdapterException.java(Compiled Code))++<br />
++at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.&lt;init&gt;(DataStoreAdapterException.java(Compiled Code))++<br />
<br />
++...............<strike>12/6/07 5:29:55:843 GMT</strike> 0000014e ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jdbc/db2Connection. The exception which was received is com.ibm.websphere.ce.cm.StaleConnectionException: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: A remote host did not respond within the timeout period.. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: C0A80899.C858.071205204713++<br />
++--12/6/07 5:29:56:007 GMT-- 0000014e ERROR E egl.dao.RefDataDAO getRefDataForDomain WebContainer : 175: A communication error has been detected. Communication protocol being used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error was detected: A remote host did not respond within the timeout period.. Communication function detecting the error: *. Protocol specific error codes(s) TCP/IP SOCKETS DB2ConnectionCorrelator: C0A80899.C858.071205204713++<br />
<br />
Looking forward to your response.<br />
<br />
Joe.

[Ken Hygh]

_Something_, 99.99% not WAS, is breaking the TCP/IP connections between
the WAS server and the Database. Most likely culprit is something in
your network.

Really.

Ken

[jolu...@hotmail.com]

Hi Ken,<br />
<br />
Thanks for your response. However, since the network guys are denying it, is there a way to fix it, or prove to them that the root of the problem is from them.<br />

<br />
Looking forward to your response.<br />

<p />
Kind regards,<br />
Joe

[Ken Hygh]

I don't know of a way to prove it.

Is there a firewall between the two boxes? This kind of thing has been
known to happen when there's a firewall between WAS and the DB server
which is configured to close connections after a certain idle time.
Since these TCP/IP connections are pooled, during periods of low traffic
they won't be used and the firewall rule may fire.

Ken