"SqlException: Statement Object Closed" Messages From Weblogic (Doc ID 1279255.1)

Last updated on SEPTEMBER 13, 2017

Applies to:

Oracle Communications ASAP - Version 4.7.2 to 5.2.4 [Release 4.7 to 5.2]
Information in this document applies to any platform.
***Checked for relevance on 14-SEP-2012***
***Checked for relevance on 04-JUL-2014***
***Checked for Currency on Sept 13, 2017***

Symptoms

Error messages in WebLogic server regarding an SQL exception:

####<Dec 2, 2010 1:36:19 PM CST> <Info> <JDBC> <asapapa6> <PRO1server> <ExecuteThread: '101' for queue: 'weblogic.kernel.Default'> <> <BEA1-12488B68E6F9767B8EB3> <BEA-001155> <The following exception has occurred:

java.sql.SQLException: JZ0S2: Statement object has already been closed.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:549)
at com.sybase.jdbc2.jdbc.SybStatement.checkDead(SybStatement.java:1949)
at com.sybase.jdbc2.jdbc.SybStatement.close(SybStatement.java:451)
at com.sybase.jdbc2.jdbc.SybStatement.close(SybStatement.java:439)
at weblogic.jdbc.wrapper.Statement.internalClose(Statement.java:349)
at weblogic.jdbc.wrapper.Connection.closeAllStatements(Connection.java:275)
at weblogic.jdbc.wrapper.Connection.closeAllStatements(Connection.java:263)
at weblogic.jdbc.wrapper.PoolConnection.doClose(PoolConnection.java:164)
at weblogic.jdbc.wrapper.PoolConnection.close(PoolConnection.java:124)
at com.mslv.asap.activation.srp.SarmProxy._submitOrder(SarmProxy.java:1127)
at com.mslv.asap.activation.srp.SarmProxy.submitOrder(SarmProxy.java:606)
at com.mslv.asap.oss.activation.JVTActivationBean.createOrderByValue(JVTActivationBean.java:565)
at com.mslv.asap.oss.activation.JVTActivation_ccenww_EOImpl.createOrderByValue(JVTActivation_ccenww_EOImpl.java:927)
at com.mslv.asap.oss.activation.XMLRequestBean.doCreateOrderByValue(XMLRequestBean.java:483)
at com.mslv.asap.oss.activation.XMLRequestBean.onMessage(XMLRequestBean.java:227)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms