Fixes are available
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Following error is getting logged at the JVM startup. 00000000 WsServerImpl A WSVR0002I: Server appserver04 open for e-business, problems occurred during startup. webcontainer E com.ibm.ws.webcontainer.WebContainer getSessionContext unable to get sessionContext java.lang.NullPointerException at com.ibm.ws.logging.WsLogger.queueAsyncEvent(WsLogger.java:828)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: During JVM startup a * * NullPointerException is thrown in * * getSessionContext unable to get * * sessionContext * **************************************************************** * RECOMMENDATION: * **************************************************************** Access to the queue that holds the asynchronous internal loggers needs to be synchronized to handle timing conditions where the queue might be emptied by the time another asynchronous logger gets queued. This is most likely to be seen with FFDC loggers as these loggers are configured to be asynchronous. The NullPointerException will occur when WsLogger.queueAsyncEvent gets invoked.
Problem conclusion
Access to the queue that holds the asynchronous internal loggers has been synchronized to handle timing conditions where the queue might be emptied by the time another asynchronous logger gets queued. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.31. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM85333
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-21
Closed date
2013-06-25
Last modified date
2013-11-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM96911
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
29 October 2021