Hi,

I'm having a random problem with the jdbc database connectivity. Seems like it's a network issue but still I have some doubts about it. The db connection gets closed because of a socket read timeout.
This is experienced on both app server.

Is there any property for the jdbc driver that would prevent it for being sensitive to network fluctuations?

The traces on the db2 engine do not reveal any database availability problem during the timeframe.

Any ideea on how to get a deeper insight?

thanks in advance

enviroment:
Windows Server 2003 x86
DB2 v9.5 fixpack 3
Application: WebSphere Portal 6.0.2 running on Websphere application server 7.0 cluster - 2 nodes

jdbc exception
[9/29/11 14:42:06:110 EEST] 00000046 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adapter for resource jdbc/relDS. The exception is: com.ibm.db2.jcc.b.tn: [jcc][t4][2030][11211][3.53.70] A communication error occurred during operations on the connection's underlying socket, socket input stream,
or socket output stream. Error location: Reply.fill(). Message: Read timed out. ERRORCODE=-4499, SQLSTATE=08001:java.net.SocketTimeoutException: Read timed out