Fixes are available
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
NullPointerException caught at com.ibm.son.mesh.CfwTCPImpl.ready (CfwTCPImpl.java:887) and logged in a ODCF8601E message within SystemOut.log after the server has shutdown and logged its stopped message (WSVR0024I). [17/04/20 5:30:02:725 JST] 00b2682a CfwTCPImpl E ODCF8601E: ????????: java.lang.Exception: Unexpected exception in ready {6c604525: 10.211.17.90 udp_port=11009 tcp_port=11010 (outgoing) remote TYOBCN60/10.211.17.90:11010 local :0} at com.ibm.son.mesh.CfwTCPImpl.ready(CfwTCPImpl.java:887) at com.ibm.ws.channel.framework.impl.OutboundVirtualConnectionI mpl.ready(OutboundVirtualConnectionImpl.java:122) at com.ibm.wsspi.channel.base.OutboundProtocolLink.ready(Outbou ndProtocolLink.java:111) at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyOutboundP ostHandshake(SSLConnectionLink.java:874) at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyHandshakeCom pletedCallback.complete(SSLConnectionLink.java:417) at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtil s.java:1072) at com.ibm.ws.ssl.channel.impl.SSLHandshakeIOCallback.complete( SSLHandshakeIOCallback.java:87) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.future Completed(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(Abstract AsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(As yncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:2 04) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(Result Handler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1865) Caused by: java.lang.NullPointerException at com.ibm.ws.channel.framework.impl.OutboundVirtualConnectionI mpl.getChannelAccessor(OutboundVirtualConnectionImpl.java:59 ) at com.ibm.son.mesh.CfwTCPImpl.readyOut(CfwTCPImpl.java:895) at com.ibm.son.mesh.CfwTCPImpl.ready(CfwTCPImpl.java:884) This is a timing window where we requested a connection from CFW and by the time they call our callback to notify us that the channel is ready, we are already in the process of shutting down. The fix is easy, when the exception is caught, check to see if the Peer state is stopping or stopped and if so don't log the benign error.  
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server WAS ND edition- Virtual * * Enterprise/IM Component * **************************************************************** * PROBLEM DESCRIPTION: NPE at * * com.ibm.son.mesh.CfwTCPImpl.ready(CfwTC * * PImpl.java:887) logged in ODCF8601E * * message after shutdown invocation. * **************************************************************** * RECOMMENDATION: * **************************************************************** A NullPointerException is caught at com.ibm.son.mesh.CfwTCPImpl.ready (CfwTCPImpl.java:887) and is logged in a ODCF8601E message within SystemOut.log after the server has shutdown and has already logged its stopped message (WSVR0024I).
Problem conclusion
The Intelligent Management Peer-to-Peer Overlay Network has been altered to properly handle this condition when the process is being shutdown such that the NullPointerException is not incurred. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.13 and 9.0.0.6. 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
PI82522
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-02
Closed date
2017-11-01
Last modified date
2018-08-20
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022