PQ63377: V4.02 SQLEXCEPTIONS ON COMMITS WHEN INFORMIX USED AS DB FOR SESSION PERSISTENCE

APAR status
Closed as program error.

Error description
This apar belongs to session component.
.
SQLExceptions being thrown on commits  when Informix is used as
database for sessions persistence.
When using Informix 9.3 for session persistence, session
invalidation fails with the errors below.
.
^7/20/02 12:15:44:017 CDT!   18cb3a HttpTransport A SRVE0171I:
Transport http is listening on port 9,081.
^7/20/02 12:15:55:289 CDT!   18cb3a Server        A WSVR0023I:
Server STWD_Clone2 open for e-business
^7/20/02 12:36:40:950 CDT!    e918a SessionContex X SESN0050E:
BackedHashtable:dropTable: Exception dropping sessions table -
You Should Drop the sessions table manually. The Session Manager
has detected that the Sessions table was in an out-of-date
format. The old table could not be dropped automatically. The
user should manually drop the sessions table and restart the
server.
.
^7/20/02 12:36:41:001 CDT!    e918a SessionContex X WTRN0047E:
java.sql.SQLException: Not in transaction.
^7/20/02 12:36:41:449 CDT!   6d079a SessionContex X SESN0037E:
BackedHashtable:pollForInvalids - database error. If a
SQLException has occurred then refer to the appropriate database
documentation for your environment. Also, assure that you have
properly configured a datasource for Session Manager. for id
null
^7/20/02 12:36:41:471 CDT!   6d079a SessionContex X WTRN0047E:
java.sql.SQLException: Not in transaction.
.
^7/20/02 12:36:41:556 CDT!   6d079a SessionContex X SESN0036E:
BackedHashtable:doInvalidations - database error. If a
SQLException has occurred then refer to the appropriate database
documentation for your environment. Also, assure that you have
properly configured a datasource for Session Manager. with id
PE1VXQJA5C2402NU23TYQIA
.
^7/20/02 12:36:41:585 CDT!   6d079a SessionContex X WTRN0047E:
java.sql.SQLException: Not in transaction.
 at
com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:348)
 at com.informix.jdbc.IfxSqli.addException(IfxSqli.java:3025)
 at com.informix.jdbc.IfxSqli.receiveError(IfxSqli.java:3335)
 at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2288)
 at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2208)
 at com.informix.jdbc.IfxSqli.executeCommit(IfxSqli.java:438)
 at
com.informix.jdbc.IfxSqliConnect.commit(IfxSqliConnect.java:1191
)
 at com.ibm.ejs.cm.pool.ConnectO.commit(ConnectO.java:2177)
 at
com.ibm.ejs.cm.proxy.ConnectionProxy.commit(ConnectionProxy.java
:620)
 at
com.ibm.servlet.personalization.sessiontracking.BackedHashtable.
doInvalidations(BackedHashtable.java:1041)
 at
com.ibm.servlet.personalization.sessiontracking.DatabaseSessionC
ontext.performInvalidation(DatabaseSessionContext.java:795)
 at
com.ibm.servlet.personalization.sessiontracking.SessionContext.p
ollInvalidations(SessionContext.java:993)
 at
com.ibm.servlet.personalization.sessiontracking.SessionContext$I
.
^7/20/02 12:36:56:569 CDT!    e918a WebGroup      I SRVE0091I:
^Servlet LOG!: LoginServlet: init
^7/20/02 12:36:56:595 CDT!    e918a SessionContex X SESN0063E:
BackedHashtable.selectNoUpdateError - Exception in
selectNoUpdate. If a SQLException has occurred then refer to the
appropriate database documentation for your environment. Also,
assure that you have properly configured a datasource for
Session Manager.PTE0QZJ25YS1QXHWIDVC4KQ
^7/20/02 12:36:56:656 CDT!    e918a SessionContex X WTRN0047E:
java.sql.SQLException: Not in transaction.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server - Session       *
*                 Manager Users                                *
****************************************************************
* PROBLEM DESCRIPTION: SQL Exceptions are being thrown on a    *
*                      commit with Informix as the sessions    *
*                      database for persistence.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The session manager uses connections in the auto commit mode for
session persistence. At certain places, the commit operation
is being called on the connection after a sql update to release
database resources which were being held because of database
bugs.  Informix 9.3 does not allow a commit to be performed and
throws SQLException unless the connection is in the scope of an
explicit transaction is created.
Problem conclusion
With this fix the session manager will not issue commits if
the database being used is Informix.
Temporary fix
PQ63377.jar
Comments
APAR information
APAR number PQ63377
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-07-20
Closed date 2002-07-30
Last modified date 2002-07-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
SESSIONS          

Fix information
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ63377
IBM Group: Software Group
Modified date: Jul 30, 2002