Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
When using dumpNamespace.sh, error similar to the following may occur (example from testcase TestEJBEAR.ear) : .... 235 (top)/applications/TestEJBEAR javax.naming.Context 236 (top)/applications/TestEJBEAR/TestEJB javax.naming.Context 237 (top)/applications/TestEJBEAR/TestEJB/TestSB!sb.TestSBRemote 237 sb.TestSBRemote 238 [Binding name not available.] [Class name not Page 5 of 58 available.] 238 ERROR: Received the following naming exception: javax.naming.NamingException: Unexpected exception occurred. [Root exception is java.lang.StackOverflowError]
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 who use EJBs and * * dumpNameSpace. * **************************************************************** * PROBLEM DESCRIPTION: Calling getCause() on * * com.ibm.ws.exception.WsEJBException * * results in an infinite loop that * * fails with a StackOverflowError. * **************************************************************** * RECOMMENDATION: * **************************************************************** When local EJB interfaces are present, and dumpNameSpace is invoked, this may result in a StackOverflowError due to an infinite loop in com.ibm.ws.exception.WsEJBException.getCause().
Problem conclusion
The infinite loop in WsEJBException has been corrected. The StackOverflowError will not occur and dumpNameSpace will complete normally. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.1. 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
PM88783
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-05-10
Closed date
2013-05-16
Last modified date
2013-05-16
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
11 January 2022