文档库 最新最全的文档下载
当前位置:文档库 › MQ开发问题

MQ开发问题

描述:两台机器,java客户端与IBM MQ服务端连接 报用户没有授权错误
解决:QM'--->'Channel'--->'服务连接'--->'MCA'
增加:MUSR_MQADMIN
如不行则运行队列管理器
通常情况下,MQ客户端(此处为WAS)与MQ服务器端通讯时,使用MQ服务器端的连接通道进行连接。
连接通道有一个属性:MCAUSER。
如果MCAUSER属性值为空,则使用MQ客户端所在的操作系统上的用户
如果MCAUSER属性值不为空,则使用该值作为MQ客户端连上来时使用的用户,该值必须是MQ服务器上的mqm组内的用户。
当客户端与服务器端通讯时,报2035错误,就是由于客户端与服务器端通讯时所使用的用户没有权限造成的

解决方法有两个,经过测试都可以成功连接。
1、如果MQ服务器端的通道定义的MCAUSER属性值为缺省值,即为空,则可将MQ客户端所使用的用户添加到MQ服务器所在的操作系统中,并把此用户加入到mqm组中。
2、查看MQ服务器端mqm组内的用户,在服务器端的服务连接通道定义中设置MCAUSER属性的值为改用户,例如windows下的默认用户为:MUSR_MQADMIN

相关命令:
1、登陆MQ 命令行,QM_KC为队列管理器名称
runmqsc QM_KC
2、查看通道定义,此处通道名称为默认的SYSTEM.DEF.SVRCONN,可以查看到MCAUSER属性
display channel(SYSTEM.DEF.SVRCONN) all
3、修改MCAUSER属性
ALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('MUSR_MQADMIN')
START CHL(SYSTEM.DEF.SVRCONN)

JMSWMQ2013: 为队列管理器 'WMQ1QM' 提供的安全性认证无效,连接方式为 'Client',主机名为 '192.168.0.179(1616)'。
请检查提供的用户名和密码在您正在连接的队列管理器中是否正确。
at https://www.wendangku.net/doc/2017774718.html,mon.internal.Reason.reasonToException(Reason.java:521)
at https://www.wendangku.net/doc/2017774718.html,mon.internal.Reason.createException(Reason.java:221)
at com.ibm.msg.client.wmq.internal.WMQConnection.(WMQConnection.java:426)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6902)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6277)
at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:285)
at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6233)
at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:6262)
at https://www.wendangku.net/doc/2017774718.html,m.mq.oper.ProducerTest.start(ProducerTest.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at https://www.wendangku.net/doc/2017774718.html,ng.reflect.Method.invoke(Method.java:597)
at org.junit

.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ 调用失败,完成代码为 '2' ( 'MQCC_FAILED' ),原因为 '2035' ( 'MQRC_NOT_AUTHORIZED' )。
at https://www.wendangku.net/doc/2017774718.html,mon.internal.Reason.createException(Reason.java:209)
... 35 more


描述:两台机java客户端与IBM MQ服务端连接 报SSL握手失错误

解决:https://www.wendangku.net/doc/2017774718.html,/support/docview.wss?uid=swg21614686&myns=swgws&mynp=OCSSFKSJ&mync=R
JMSWMQ0018: 连接至队列管理器 'WMQ1QM' 失败,连接方式为 'Client',主机名为 '192.168.0.170(1616)'。
检查队列管理器是否已启动,如果正在以客户机方式运行,那么还要检查是否有侦听器在运行。请参阅链接的异常以获取更多信息


at https://www.wendangku.net/doc/2017774718.html,mon.internal.Reason.reasonToException(Reason.java:585)
at https://www.wendangku.net/doc/2017774718.html,mon.internal.Reason.createException(Reason.java:221)
at com.ibm.msg.client.wmq.internal.WMQConnection.(WMQConnection.java:426)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6902)
at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6277)
at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:285)
at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6233)
at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:6262)
at https://www.wendangku.net/doc/2017774718.html,m.mq.oper.ProducerTest.start(ProducerTest.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at https://www.wendangku.net/doc/2017774718.html,ng.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit

.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ 调用失败,完成代码为 '2' ( 'MQCC_FAILED' ),原因为 '2397' ( 'MQRC_JSSE_ERROR' )。
at https://www.wendangku.net/doc/2017774718.html,mon.internal.Reason.createException(Reason.java:209)
... 35 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9204: 与主机 '192.168.0.170(1616)' 的连接被拒绝。 [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2397;AMQ9771: SSL 握手失败。 [1=https://www.wendangku.net/doc/2017774718.html,.ssl.SSLHandshakeException[Remote host closed connection during handshake],3=atwasoft/192.168.0.170:1616 (atwasoft),4=SSLSocket.startHandshake,5=default]],3=192.168.0.170(1616),5=RemoteTCPConnection.protocolConnect]
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:2053)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1226)
at com.ibm.mq.ese.jmqi.InterceptedJmqiImpl.jmqiConnect(InterceptedJmqiImpl.java:311)
at com.ibm.mq.ese.jmqi.ESEJMQI.jmqiConnect(ESEJMQI.java:337)
at com.ibm.msg.client.wmq.internal.WMQConnection.(WMQConnection.java:346)
... 34 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2397;AMQ9771: SSL 握手失败。 [1=https://www.wendangku.net/doc/2017774718.html,.ssl.SSLHandshakeException[Remote host closed connection during handshake],3=atwasoft/192.168.0.170:1616 (atwasoft),4=SSLSocket.startHandshake,5=default]
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:1187)
at com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConnection.java:724)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSessionFromNewConnection(RemoteConnectionSpecification.java:400)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionSpecification.getSession(RemoteConnectionSpecification.java:299)
at com.ibm.mq.jmqi.remote.impl.RemoteConnectionPool.getSession(RemoteConnectionPool.java:164)
at com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:1598)
... 38 more
Caused by: https://www.wendangku.net/doc/2017774718.html,.ssl.SSLHandshakeException: Remote host closed connection during handshake
at https://www.wendangku.net/doc/2017774718.html,.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:808)
at https://www.wendangku.net/doc/2017774718.html,.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112)
at https://www.wendangku.net/doc/2017774718.html,.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139)
at https://www.wendangku.net/doc/2017774718.html,.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection$6.run(RemoteTCPConnection.java:1156)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection$6.run(RemoteTCPConnection.java:11

51)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:1149)
... 43 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at https://www.wendangku.net/doc/2017774718.html,.ssl.internal.ssl.InputRecord.read(InputRecord.java:333)
at https://www.wendangku.net/doc/2017774718.html,.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
... 50 more

相关文档