Fixes are available
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
The message provided when the configuration for the CRA is incorrect is difficult to understand. We need to add the following details adjunct_region_server_configured_to_bus: NOT SET, DEFAULT=0 to the exception message The server is not configured with a CRA The full exception: ExtendedMessage: Entry; java.io.IOException at com.ibm.ws.tcpchannelproxy.jfap.impl.TCPProxyOutboundConnectorLi nk.connect(TCPProxyOutboundConnectorLink.java:149) at com.ibm.ws.tcpchannelproxy.jfap.impl.TCPProxyOutboundConnectorLi nk.connectAsynch(TCPProxyOutboundConnectorLink.java:76) at com.ibm.wsspi.channel.base.OutboundProtocolLink.connectAsynch(Ou tboundProtocolLink.java:103) at com.ibm.ws.channel.framework.impl.OutboundVirtualConnectionImpl. connectAsynch(OutboundVirtualConnectionImpl.java:71) at com.ibm.ws.sib.jfapchannel.framework.impl.CFWNetworkConnection.c onnectAsynch(CFWNetworkConnection.java:175) at com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionDataGroup.co nnectOverNetwork(ConnectionDataGroup.java:777) at com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionDataGroup.do Connect(ConnectionDataGroup.java:715) at com.ibm.ws.sib.jfapchannel.impl.octracker.ConnectionDataGroup.co nnect(ConnectionDataGroup.java:673) at com.ibm.ws.sib.jfapchannel.impl.octracker.OutboundConnectionTrac ker.connect(OutboundConnectionTracker.java:659) at com.ibm.ws.sib.jfapchannel.impl.ClientConnectionManagerImpl.conn ect(ClientConnectionManagerImpl.java:184) at com.ibm.ws.wmqra.jfap.WMQRAJFAPCommunicator.connect(WMQRAJFAPCom municator.java) at com.ibm.ws.wmqra.jfap.WMQRAJFAPCommunicator.alarm(WMQRAJFAPCommu nicator.java:264) at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:133) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1700) Caused by: com.ibm.ws.tcpchannelproxy.jfap.NotValidInCurrentStateException: The server is not configured with a CRA at com.ibm.ws.tcpchannelproxy.jfap.TCPProxyBridgeServicesImpl.conne ct(TCPProxyBridgeServicesImpl.java:485) at com.ibm.ws.tcpchannelproxy.jfap.impl.TCPProxyOutboundConnectorLi nk.connect(TCPProxyOutboundConnectorLink.java:136) ... 13 more If you use activation specifications with WebSphere MQ message-driven beans (MDBs) on the z/OSᄅ platform, you must enable the control region adjunct (CRA) process of the application server. Either select Enable JCA based inbound message delivery on the JMS provider settings panel, or by use the manageWMQ command to include starting the CRA as part of the process for starting an application server.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Configuration errors configuring * * WebSphere MQ activation * * specifications * * in WebSphere Application Server for * * z/OS are difficult to diagnose. * **************************************************************** * RECOMMENDATION: * **************************************************************** If you use activation specifications with WebSphere MQ message-driven beans (MDBs) on the z/OS platform, you must enable the control region adjunct (CRA) process of the application server. Either select Enable JCA based inbound message delivery on the JMS provider settings panel, or use the manageWMQ command to include starting the CRA as part of the process for starting an application server. When the CRA is not correctly configured, the resulting error messages are unclear and difficult to diagnose.
Problem conclusion
Exception text was clarified to make these types of configuration problems easier to diagnose. APAR PI19751 is currently targeted for inclusion in Fix Pack 8.0.0.10 and 8.5.5.4 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
PI19751
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-06-11
Closed date
2014-07-08
Last modified date
2014-07-28
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:
27 April 2022