My Oracle Support Banner

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

Last updated on FEBRUARY 21, 2019

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***
***Checked for Currency on Aug-28-2018***


Error messages in WebLogic server regarding an SQL exception:

####<Dec 2, 2010 1:36:19 PM CST> <Info> <JDBC> <> <

java.sql.SQLException: JZ0S2: Statement object has already been closed.
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(
at com.sybase.jdbc2.jdbc.SybStatement.checkDead(
at com.sybase.jdbc2.jdbc.SybStatement.close(
at com.sybase.jdbc2.jdbc.SybStatement.close(
at weblogic.jdbc.wrapper.Statement.internalClose(
at weblogic.jdbc.wrapper.Connection.closeAllStatements(
at weblogic.jdbc.wrapper.Connection.closeAllStatements(
at weblogic.jdbc.wrapper.PoolConnection.doClose(
at weblogic.jdbc.wrapper.PoolConnection.close(
at com.mslv.asap.activation.srp.SarmProxy._submitOrder(
at com.mslv.asap.activation.srp.SarmProxy.submitOrder(
at com.mslv.asap.oss.activation.JVTActivationBean.createOrderByValue(
at com.mslv.asap.oss.activation.JVTActivation_ccenww_EOImpl.createOrderByValue(
at com.mslv.asap.oss.activation.XMLRequestBean.doCreateOrderByValue(
at com.mslv.asap.oss.activation.XMLRequestBean.onMessage(
at weblogic.ejb20.internal.MDListener.execute(
at weblogic.ejb20.internal.MDListener.onMessage(
at weblogic.jms.client.JMSSession.onMessage(
at weblogic.jms.client.JMSSession.execute(
at weblogic.kernel.ExecuteThread.execute(


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.