WAS7: Troubleshooting SQL socket write errors - Websphere

This is a discussion on WAS7: Troubleshooting SQL socket write errors - Websphere ; We are having issues with the occasional "java.sql.SQLException: Connection reset by peer: socket write error" from an application deployed on WAS 7.0.0.3. It seems as if the connection isn't open when the client application tries to use it. I suspect ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: WAS7: Troubleshooting SQL socket write errors

  1. WAS7: Troubleshooting SQL socket write errors

    We are having issues with the occasional "java.sql.SQLException: Connection reset by peer: socket write error" from an application deployed on WAS 7.0.0.3.

    It seems as if the connection isn't open when the client application tries to use it. I suspect that it has to do something with connection pooling, connection validation and/or configuration of SQL Server 2005.

    The application that's being affected if proprietary and we have no access to the source code, but I suspect that the problem lies somewhere in the container-connection pool-jdbc driver-sql server stack, and not in the application.

    Any ideas on how to troubleshoot these kinds of issues? Logging of connection pool states/operations?

    System information:
    JDBC driver: Microsoft SQL Server 2005 JDBC Driver 1.2.2828.100
    OS: Windows Server 2003 5.2 build 3790 Service Pack 2
    WAS: 7.0.0.3
    SQL Server: 9.00.3239.00, SP2, Standard Edition

    Example stack trace:
    {code}
    [2009-08-31 08:46:53:759 CEST] 00000016 XATransaction E J2CA0027E: An exception occurred while invoking start on an XA Resource Adapter from DataSource PREFSXA, within transaction ID {XidImpl: formatId(57415344), gtrid_length(36), bqual_length(54),
    data(000001236f34c9f10000000100016e81d462629324e2c 2cc6d0dca0c0c880bcc6b668c97000001236f34c9f10000000 100016e81d462629324e2c2cc6d0dca0c0c880bcc6b668c970 00000010000000000000000000000000001)} : javax.transaction.xa.XAException: java.sql.SQLException: Connection reset by peer: socket write error
    at com.microsoft.sqlserver.jdbc.SQLServerXAResource.s tart(Unknown Source)
    at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.start (WSRdbXaResourceImpl.java:1506)
    at com.ibm.ejs.j2c.XATransactionWrapper.start(XATrans actionWrapper.java:1454)
    at com.ibm.ws.Transaction.JTA.JTAResourceBase.start(J TAResourceBase.java:148)
    at com.ibm.tx.jta.RegisteredResources.startRes(Regist eredResources.java:988)
    at com.ibm.ws.tx.jta.RegisteredResources.enlistResour ce(RegisteredResources.java:1099)
    at com.ibm.ws.tx.jta.TransactionImpl.enlistResource(T ransactionImpl.java:2099)
    at com.ibm.ws.tx.jta.TranManagerSet.enlist(TranManage rSet.java:515)
    at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATran sactionWrapper.java:708)
    at com.ibm.ejs.j2c.ConnectionManager.lazyEnlist(Conne ctionManager.java:2126)
    at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImp l.lazyEnlist(WSRdbManagedConnectionImpl.java:2547)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTr ansactionIfNecessary(WSJdbcConnection.java:712)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepare Statement(WSJdbcConnection.java:2743)

    {code}

  2. Re: WAS7: Troubleshooting SQL socket write errors

    I am not sure about MS SQL 2005,
    but there is some information relating to this error:http://www-01.ibm.com/support/docvie...id=swg21215890

  3. Re: WAS7: Troubleshooting SQL socket write errors

    Thank you for your answer, Nagu.

    The error and the fix you mentioned seem to be regarding XA transactions, which is not the issue we are having. XA transactions is enabled on SQL Server 2005 and are working fine.
    The issue is the occasional errors which I suspect have something to do with the long running and idle open connections.

    The question is how we go about troubleshooting this.

+ Reply to Thread