java.sql.SQLException: Io exception: Connection reset by peer: socket write error

Rob Fleming

unread,

Mar 12, 2002, 10:20:54 AM3/12/02

to

We are encountering the following error on our Production wlserver:

Message: EJB-Utility
Class: package com.sprint.bln.ejb.utility.com.sprint.bln.ejb.utility.RadUserTokenAdminImpl
Method: getfeatures
java.sql.SQLException: Io exception: Connection reset by peer: socket write error
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:210)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:323)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1460)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1371)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1900)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:407)
at weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:45)
at weblogic.jdbc.rmi.internal.PreparedStatementImpl.execute(PreparedStatementImpl.java:289)
at weblogic.jdbc.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.java:398)
at com.sprint.bln.ejb.cage.RadPropertyAdmin.getPropertyInstancesByDeviceInstanceId(RadPropertyAdmin.java:491)
at com.sprint.bln.ejb.cage.RadPropertyAdminImpl.getPropertyInstancesByDeviceInstanceId(RadPropertyAdminImpl.java:150)
at com.sprint.bln.ejb.cage.RadPropertyAdminEOImpl.getPropertyInstancesByDeviceInstanceId(RadPropertyAdminEOImpl.java:105)
at com.sprint.bln.ibl.cage.RadPropertyInstanceList.getPropertyInstancesByDeviceInstanceId(RadPropertyInstanceList.java:31)
at jsp_servlet._cagedeviceiplistview._jspService(_cagedeviceiplistview.java:227)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:213)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1631)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
************* Log Entry *************
Message: Exception been thrown
Class: package com.sprint.bln.ejb.cage.com.sprint.bln.ejb.cage.RadPropertyAdminImpl
Method: getPropertyInstancesByDeviceInstanceId(long deviceInstanceId)
Exception:
java.sql.SQLException: Io exception: Connection reset by peer: socket write error

We have the following configuration:
WLServer 6.0 SP2
Oracle 8.1.7
Oracle Thin JDBC driver 8.1.7

Our connection pool has the following configuration:
Connections:
- Initial Capacity: 10
- Maximum Capacity: 30
- Capacity Increment: 5
- Login Delay Seconds: 0
- Refresh Period: 1
- Allow Shrinking: 'Selected'
- Shrink Period: 1

Testing:
- Test Table Name: dual
- Test Reserved Connections: 'Not Selected'
- Test Released Connections: 'Not Selected'

Why is this occuring and how do we resolve it? Each time the error happens I
have to bounce the server.

Thanks,
Rob

Joseph Weinstein

unread,

Mar 12, 2002, 12:37:43 PM3/12/02

to Rob Fleming

this just means the DBMS has killed the connection. If you set your pool to
test connections before giving them to you, it will replace broken ones before
you get them. (select Test Reserved Connections).
joe

Allen Miller

unread,

May 1, 2002, 7:50:54 PM5/1/02

to

We have the same problem (WLS 6.1 SP 1) and we have both 'test reserved connections'
and 'test released connections' set to on.

We tried SP2 but it caused other problems. Is SP 2 supposed to handle this problem?

Joseph Weinstein

unread,

May 2, 2002, 12:59:14 PM5/2/02

to Allen Miller

Allen Miller wrote:

> We have the same problem (WLS 6.1 SP 1) and we have both 'test reserved connections'
> and 'test released connections' set to on.
>
> We tried SP2 but it caused other problems. Is SP 2 supposed to handle this problem?

You should only have test reserved connections. The other is a waste. To repeat, this
does not yet show any symptoms of being a weblogic problem. It seems the DBMS is
killing the connection. You should download and use the latest driver from Oracle, in
case it is a driver bug.
Joe

Allen Miller

unread,

May 2, 2002, 2:09:07 PM5/2/02

to

We're using weblogic.jdbc.oci.xa.XADataSource, is there an update for this driver?