Question & Answer
When starting up standalone Liberty CICS Transaction Server for z/OS (CICS TS) regions, why am I receiving the following exception:
LP2SSA6 : ?err? : java.rmi.server.ExportException: Port already in use: 0; nested exception is: .java.net.BindException: EDC8116I Address not available. (Bind failed) and Caused by: com.ibm.msg.client.jms.DetailedIllegalStateException: JMSWMQ0018: Failed to connect to queue manager 'xxxxx' with connection mode 'Client' and host name '10.0.19.9(9322)'. Check the queue manager is started and if running in client mode, check there is a listener running. Please see the linked exception for more information. Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE'). .at com.ibm.msg.client.wmq.common.internal.Reason.createException (Reason.java:203) .... 33 more
The following errors were written to the DFHJVMERR file:
J2CA8802E: The message endpoint activation failed for resource adapter wmqJms due to exception:
MQJCA1011: Failed to allocate a JMS connection., error code: MQJCA1011 An internal error caused an attempt to allocate a connection to fail. See the linked exception for details of the failure.
JMSWMQ0018: Failed to connect to queue manager 'XXXX' with connection mode 'Client' and host name 'XXXX.yyyyyy.zzzzz(9322)'.
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2538' ('MQRC_HOST_NOT_AVAILABLE')
After adding an EXEC statement for PGM=BPXTCAFF,PARM=TCPIP to the JCL for the CICS region's running standalone Liberty, the 'MQCC_FAILED' with reason '2538' 'MQRC_HOST_NOT_AVAILABLE' error no longer occurred and the standalone Liberty CICS regions started.
CICS/TS CICSTS CICS TS CICS Transaction Server
17 September 2018