IO09477: WITH WEBSPHERE CONNECTION POOLING ENABLED ON AN ORACLE LIBRARY SERVER DATABASE, STATEMENT HANDLES MAY BE PREMATURELY CLOSED.

APAR status

• Closed as program error.

Error description

• With WebSphere Connection Pooling enabled on an Oracle
  Library Server database, in certain situtations, the Content
  Manager APIs may generate exceptions that contain the following
  entry:
  
  class com.ibm.ejs.cm.proxy.OracleCallableStatementProxy is
  closed
  
  
  An example of an excerpt from a stack trace is as follows:
  
  
  com.ibm.mm.beans.CMBConnection
  com.ibm.mm.beans.CMBException: class
  com.ibm.ejs.cm.proxy.OracleCallableStatementProxy is closed
  com.ibm.websphere.ce.cm.StaleConnectionException: class
  com.ibm.ejs.cm.proxy.OracleCallableStatementProxy is closed
   at
  com.ibm.ejs.cm.proxy.StatementProxy.getStatement(StatementProxy.
  java(Compiled Code))
   at
  com.ibm.ejs.cm.proxy.PreparedStatementProxy.clearParameters(Prep
  aredStatementProxy.java:208)
   at
  com.ibm.mm.sdk.internal.sql.oracle.POraCallableStatementICM.clea
  nup(POraCallableStatementICM.java(Compiled Code))
   at
  com.ibm.mm.sdk.internal.sql.oracle.POraCallableStatementICM.clos
  e(POraCallableStatementICM.java:421)
   at
  com.ibm.mm.sdk.server.PMoveObjectICM.moveObject(PMoveObjectICM.j
  ava:487)
  ...
  
  The above stack trace showing the exception, occurs when a
  document is being re-indexed from one item type to another item
  type (when WebSphere Connection Pooling is enabled and the
  Library Server database is running on Oracle)
  
  There are other operations which can also generate, when
  WebSphere Connection Pooling is enabled and the Library Server
  database is running on Oracle, the exception that includes the
  message:
  
  class
  com.ibm.ejs.cm.proxy.OracleCallableStatementProxy is closed
  

Local fix

• Turn off WebSphere Connection Pooling
  

Problem summary

• When using WebSphere Application Server connection pooling
  against an Oracle Content Manager database, database statement
  handles are prematurely closed.
  

Problem conclusion

• This problem was fixed in DB2 Content Manager Version 8.3 Fix
  Pack 10. The Content Manager connector will close statement
  handles before a commit/rollback of a transaction in the
  WebSphere Application Server environment.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CM CONNECT V8

• Fixed component ID

  5724B43A1

Applicable component levels