APAR status
Closed as program error.
Error description
Synchronization in DatabaseSessionData.toString can cause a hang
in certain exception scenarios. For example, if a
java.io.InvalidClassException is thrown when retrieving an
object from the session object (BackedHashtable.getValue) the
session manager will print out the "session object internals"
into the logs. This will call the DatabaseSessionData.toString
method. Since this method is synchronized, it can cause a hang
condition. It is proposed that this synchronization be removed.
This should have been removed as a result of
PQ83345.
PQ83345
only removed the synchronization in DatabaseSessionData.
However, DatabaseSessionData.toString() calls
SessionData.toString() (i.e. super.toString()) which is
synchronized.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Servers users of *
* Http sessions. *
****************************************************************
* PROBLEM DESCRIPTION: StaleConnectionException occurs when *
* Application Server cleans up timed-out *
* sesisons. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The debug print statement of SessionContext is causing the
following exception:
17:15:52:738 EST] 364b53 ConnectionEve
A J2CA0056I: The Connection
Manager received a fatal connection error
from the Resource Adaptor for
resource jdbc/Session DataSource. The
exception which was received is
com.ibm.websphere.ce.cm.StaleConnection
Exception: [IBM][CLI
Driver][DB2/SUN] SQL1224N A database
agent could not be started to
service a request, or was terminated as
a result of a database system
shutdown or a force command.
SQLSTATE=55032
[3/25/04 17:15:52:774 EST] 364b53
SessionContex E SESN0016E:
DatabaseSessionContext:performInvalidation
detected an error. The
database invalidation of timed out sessions
has encountered an error. If
a SQLException has occurred then refer to
the appropriate database
documentation for your environment. Also,
ensure that you have properly
configured a datasource for Session
Manager.
[3/25/04 17:15:52:786 EST] 364b53
SessionContex E Exception is:
com.ibm.websphere.ce.cm.StaleConnection
Exception: [IBM][CLI
Driver][DB2/SUN] SQL1224N A database
agent could not be started to
service a request, or was terminated as
a result of a database system
shutdown or a force command.
SQLSTATE=55032
Problem conclusion
Removed one debug statement from code so SessionConext will
not get printed to avoid this problem.
Temporary fix
tmp fix sent to L2/customer.
Comments
APAR information |
APAR number |
PQ87534 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-04-14 |
Closed date |
2004-07-12 |
Last modified date |
2004-07-12 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|