Fixes are available
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.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
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.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
An EJB lookup or an EJB method invocation might hang if the remote server encounters a problem decrypting the data stream comprising the remote request.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Hangs may occur using TCP connections * * to a WebSphere Application Server for * * z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** An unexpected exception, such as a com.ibm.crypto.hdwrCCA.provider.JCECCARuntimeException, was thrown under the ZAioTCPReadRequestContextImpl.readCompleted, ZAioTCPWriteRequestContextImpl.writeCompleted, or the ZIOPChannelBridge.sendMessage invocations. The processing of this unexpected exception resulted in abandoning the connection without proper cleanup. The other-side of the connection experienced a non-responsive connection. The following examples illustrate the failures seen: com.ibm.crypto.hdwrCCA.provider.JCECCARuntimeException: Hardware error from call CSNBOWH returnCode 12 reasonCode 0 ... at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext. decryptMessage(SSLReadServiceContext.java:1213) at com.ibm.ws.ssl.channel.impl. SSLReadServiceContext$SSLReadCompletedCallback.complete (SSLReadServiceContext.java:1767) at com.ibm.ws.tcp.channel.impl. ZAioTCPReadRequestContextImpl.readCompleted( ZAioTCPReadRequestContextImpl.java:682) at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink. readCompleted(ZAioTCPConnLink.java:1206) at com.ibm.ws.tcp.channel.impl.ZAioTCPChannel. readCompleted(ZAioTCPChannel.java:929) at com.ibm.ws.tcp.channel.impl.ZAioTCPChannelCPPUtilities. readCompleted(ZAioTCPChannelCPPUtilities.java:181) Trace: 2013/03/25 13:25:26.232 02 t=6C09C0 c=0.2A key=S2 tag= (13007004) SourceId: com.ibm.ws390.ziop.ZIOPChannelBridge ExtendedMessage: send_message; com.ibm.crypto.hdwrCCA. provider.JCECCARuntimeException: Hardware error from call CSNBOWH returnCode 12 reasonCode 0 at com.ibm.crypto.hdwrCCA.provider.MD5.a(MD5.java:87) at com.ibm.crypto.hdwrCCA.provider.MD5.engineDigest( MD5.java:52) at java.security.MessageDigest$MessageDigestImpl. engineDigest(MessageDigest.java:357) at java.security.MessageDigest.digest( MessageDigest.java:206) at com.ibm.crypto.hdwrCCA.provider.HmacMD5.engineDoFinal( HmacMD5.java:73) at javax.crypto.Mac.doFinal(Unknown Source) at com.ibm.jsse2.yb.a(yb.java:60) at com.ibm.jsse2.yb.a(yb.java:30) at com.ibm.jsse2.d.a(d.java:4) at com.ibm.jsse2.e.a(e.java:67) at com.ibm.jsse2.y.a(y.java:53) at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:154) at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:41) at com.ibm.jsse2.SSLEngineImpl.a(SSLEngineImpl.java:80) at com.ibm.jsse2.SSLEngineImpl.wrap(SSLEngineImpl.java:130) at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:3) at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext. encryptMessage(SSLWriteServiceContext.java:614) at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext. encryptAndWriteAsync(SSLWriteServiceContext.java:398) at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext. write(SSLWriteServiceContext.java:329) at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext. write(SSLWriteServiceContext.java:175) at com.ibm.ws390.channel.ziop.ZIOPOutboundMessageHandler. writeMessage(ZIOPOutboundMessageHandler.java:104) at com.ibm.ws390.channel.ziop.ZIOPConnectionContext. writeMessage(ZIOPConnectionContext.java:215) at com.ibm.ws390.ziop.ZIOPChannelBridge.sendMessage( ZIOPChannelBridge.java:1049) at com.ibm.ws390.ziop.ZIOPCPPUtilities. process_inbound_request(Native Method) at com.ibm.ws390.channel.ziop.ZIOPInboundConnLink. routeIncomingMessage(ZIOPInboundConnLink.java:220) at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler. readComplete(ZIOPInboundMessageHandler.java:292) at com.ibm.ws390.channel.ziop.ZIOPInboundMessageHandler. complete(ZIOPInboundMessageHandler.java:228) at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext $SSLReadCompletedCallback.complete( SSLReadServiceContext.java:1784) at com.ibm.ws.tcp.channel.impl. ZAioTCPReadRequestContextImpl.readCompleted( ZAioTCPReadRequestContextImpl.java:682) at com.ibm.ws.tcp.channel.impl.ZAioTCPConnLink. readCompleted(ZAioTCPConnLink.java:1206) at com.ibm.ws.tcp.channel.impl.ZAioTCPChannel. readCompleted(ZAioTCPChannel.java:929) at com.ibm.ws.tcp.channel.impl.ZAioTCPChannelCPPUtilities. readCompleted(ZAioTCPChannelCPPUtilities.java:181)
Problem conclusion
Code has been modified in the ZAioTCPReadRequestContextImpl.readCompleted, ZAioTCPWriteRequestContextImpl.writeCompleted, and the ZIOPChannelBridge.sendMessage routines to properly handle unexpected exceptions. This should result in the connection closing. APAR PI16990 is currently targeted for inclusion in Fix Packs 8.0.0.10 and 8.5.5.3 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI16990
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-29
Closed date
2014-05-15
Last modified date
2014-05-15
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 April 2022