Unable to connect to MQ server.
Article ID: KB0084766
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
Connecting to MQ throws the following exception.
Symptoms:
The log will also have the following stack trace printed.
Cause:
Some old MQ servers/client JARs are unable to support certificates that have a "DC" or "OID"(POSTCODE) field. You will see errors such as { SSL invalid peer name, channel '?', attribute 'OID.2.5.4.17 (x2)'.} or {SSL invalid peer name, channel '?', attribute 'DC (x2)'}.
Connecting to MQ throws the following exception.
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2399;AMQ9204: Connection to host 'dbusmq-su00025.svc.db.com(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2399;AMQ9640: SSL invalid peer name, channel '?', attribute 'DC (x2)'. [5=DC (x2)]],3=dbusmq-su00025.svc.db.com(1414),5=RemotePeerName.setValue]
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1862)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1144)
at com.ibm.msg.client.wmq.internal.WMQSession.connect(WMQSession.java:330)
... 23 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2399;AMQ9640: SSL invalid peer name, channel '?', attribute 'DC (x2)'. [5=DC (x2)]
at com.ibm.mq.jmqi.remote.util.RemotePeerName.setValue(RemotePeerName.java:383)
at com.ibm.mq.jmqi.remote.util.RemotePeerName.parseDN(RemotePeerName.java:207)
at com.ibm.mq.jmqi.remote.util.RemotePeerName.<init>(RemotePeerName.java:92)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:1172)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:682)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:347)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:259)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:144)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1491)
... 25 more
Symptoms:
The log will also have the following stack trace printed.
linked JMS exception: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2399' ('MQRC_SSL_PEER_NAME_ERROR').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:204)
at com.ibm.msg.client.wmq.internal.WMQSession.connect(WMQSession.java:374)
at com.ibm.msg.client.wmq.internal.WMQSession.<init>(WMQSession.java:282)
at com.ibm.msg.client.wmq.internal.WMQConnection.createSession(WMQConnection.java:878)
at com.ibm.msg.client.jms.internal.JmsConnectionImpl.createSession(JmsConnectionImpl.java:582)
at com.ibm.msg.client.jms.internal.JmsQueueConnectionImpl.createQueueSession(JmsQueueConnectionImpl.java:143)
at com.ibm.mq.jms.MQQueueConnection.createQueueSession(MQQueueConnection.java:135)
at com.tibco.plugin.share.jms.impl.JMSSender.init(Unknown Source)
at com.tibco.plugin.jms.JMSAbstractTransmitActivity.init(Unknown Source)
at com.tibco.pe.core.TaskImpl.init(Unknown Source)
at com.tibco.pe.core.WorkflowBuilder.a(Unknown Source)
at com.tibco.pe.core.WorkflowBuilder.a(Unknown Source)
at com.tibco.pe.core.WorkflowBuilder.build(Unknown Source)
at com.tibco.pe.core.WorkflowLoader.setWorkflows(Unknown Source)
at com.tibco.pe.core.WorkflowLoader.loadWorkflows(Unknown Source)
at com.tibco.pe.core.JobPoolConfigurator.a(Unknown Source)
at com.tibco.pe.core.JobPoolConfigurator.if(Unknown Source)
at com.tibco.pe.core.JobPool.<init>(Unknown Source)
at com.tibco.pe.core.JobPoolCreator.init(Unknown Source)
at com.tibco.pe.core.JobPoolCreator.<init>(Unknown Source)
at com.tibco.pe.PEMain.a(Unknown Source)
at com.tibco.pe.PEMain.do(Unknown Source)
at com.tibco.pe.PEMain.a(Unknown Source)
at com.tibco.pe.PEMain.<init>(Unknown Source)
at com.tibco.pe.PEMain.main(Unknown Source)
Cause:
Some old MQ servers/client JARs are unable to support certificates that have a "DC" or "OID"(POSTCODE) field. You will see errors such as { SSL invalid peer name, channel '?', attribute 'OID.2.5.4.17 (x2)'.} or {SSL invalid peer name, channel '?', attribute 'DC (x2)'}.
Issue/Introduction
Unable to connect to MQ server.
Resolution
Either of the following options should help.
1). Upgrade MQ client to version 7.1.0.3 .
1). Upgrade MQ client to version 7.1.0.3 .
2). Use a certificate on the MQ server side that does not have a "DC" or "OID" field. Remember to remove any value for "Peer Name" field in the "Connection Factory" SSL configuration.
See the attached (Filename: MQSSLPeerName.PNG) for reference.
Additional Information
http://www-01.ibm.com/support/docview.wss?uid=swg1IV53739
Find the Fix Pack 7.1.0.3 for WebSphere MQ V7.1 link on the page :
http://www-01.ibm.com/support/docview.wss?uid=swg1IC83494
Find the Fix Pack 7.1.0.3 for WebSphere MQ V7.1 link on the page :
http://www-01.ibm.com/support/docview.wss?uid=swg1IC83494
Attachments
Feedback
Yes
No
Powered by
