当前位置: 首页 > 知识库问答 >
问题:

无法从WAS7创建MQ会话

葛骏
2023-03-14

WAS版本:-7.0.0.35(64位)OS-Redhat Enterprise Linux 5.8x86_64 WebSphere MQ:-7.5

注意:-MQ和WAS服务器安装在不同的机器上。传输类型TCP is用于MQ。

WAS配置:服务器级别的Classloader策略是::Single Class loading模式是::Classes首先用父类loader加载。

应用程序级别的Classloader策略是先用父类加载器加载::Classes。

我们发现以下错误的MQ日志-

进程(8240.4)用户(mqm)程序(amqrmppa)主机(mq-qa1.xxxfintech.com)安装(Installation1)VRMF(7.5.0.0)QMgr(krishnendur.lllmv.xxxfintech.com)

[2015-08-19 13:43:37,835]-[WARN]-[bContainer:10]-[com.abc.aspectfailover.ajc$before$com_xxx__aspectfailover$3$73CA82FF(){82}]-通用异常javax.jms.jmsexception:cc=2;rc=2009

    at com.abc.inf.QueueConnectionFactoryBean.createQueueConnection(QueueConnectionFactoryBean.java:159)
    at com.abc.inf.JmsConnectionFactoryImpl.newSession(JmsConnectionFactoryImpl.java:67)
    at com.abc.inf.QueueHandler.<init>(QueueHandler.java:115)
    at com.abc.inf.QueueHandlerFactory.getHandler(QueueHandlerFactory.java:51)
    at com.abc.ref.web.base.AbstractWizardController.commitAction(AbstractWizardController.java:1055)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:176)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:436)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:424)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:669)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:585)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1694)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1635)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:149)
    ....
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:191)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:516)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:307)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:84)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1662)

[2015-08-19 13:43:37,837]-[ERROR]-[bContainer : 10]-[applicationclass.QueueXXX.<init>(){118}]-javax.jms.JMSException: CC=2;RC=2009
[2015-08-19 13:43:37,837]-[WARN ]-[bContainer : 10]-[applicationclass.AFOXXX.ajc$before$cxxxxxxx(){82}]-Generic Exception
applicationclass.MKEClass: **Failed To Create MQ Session**
    at applicationclass.QueueXXX.<init>(QueueXXX.java:119)
    at applicationclass.QueueXXXZZZ.getHandler(QueueXXXZZZ.java:51)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:176)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:436)
    at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:424)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:669)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:585)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1694)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1635)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:149)
    ....
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:516)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:307)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:84)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1662)

但是我们在WAS日志中发现了错误代码-

>

  • 与MQbind相关的错误代码**mqjbnd级别:-cc=2;rc=2495;amq8568**

    类名:-Class com.ibm.msg.client.wmq.factories.wmqComponent

    组件名称:-com.ibm.msg.client.wmq

    组件标题:-IBM WebSphere MQ

    JMS系统NUM概述。连接数:1 num。会话:0。消费者:0。生产者:0

    ……queueManagerName:-xxxst2.xxxmv.aaafintech.com

    XMSC_CONNECTION_TYPE:-1

                             FFDC 
    
                                    FDCTitle
    

    ProbeID:-XN00100C

    Thread:-name=webcontainer:10 priority=5 group=main ccl=com.ibm.ws.classloader.compoundClassloader@11621162[war:xxxmv-lll-qa/yyy-tomcat.war]

    ...parent:com.ibm.ws.classloader.compoundClassloader@f120f12[app:xxxmv-lll-qa]

                                      Data
                                      ----
    
                              Version information
                              -------------------
    

    用于Java Message Service 7.0.0.0k700-L080820产品的WebSphere MQ类

    Java Message Service Client 7.0.0.0k700-L080820生产

    IBM WebSphere MQ 7.0.0.0k700-L080820生产

                                  Stack trace
                                  -----------
    

    克里希南杜

  • 共有1个答案

    寿和通
    2023-03-14

    此问题的原因是IBM MQ APAR“IV36766:MQ V7.0.0.0 JAVA CLIENT APPLICATION CONNECTING TO MQ V7.1 QMGR GETS AMQ9504 PROTOCOL Error;FDC HAS PROBE IDS RM680037 rm039000”

    问题摘要

    受影响的用户:

    V7.0.0.0 JMS客户机流中存在一个bug,该bug在代码的后续版本中得到了修复。在V7.1之前的队列管理器上,没有检测到无效流。

    在V7.1中添加了代码来检测和报告无效流,这种检测导致生成rrcE_PROTOCOL_ERROR FDCs。

    问题结论

     类似资料:
    • 这是因为我在一个搜索字段上有一个失败的Behat测试-这个字段是通过javascript添加的,所以我假设Selenium(与我的设置)有问题。 我发现,如果我访问http://localhost:4444/wd/hub并单击“create Session”,选择任何浏览器(android、iphone、firefox、chrome、internet explorer、opera),我将得到错误消

    • org.openqa.selenium.SessionNotCreatedException:无法创建新会话。(原始错误:命令失败:C:\Windows\system32\cmd.exe/s/C“C:\Program Files(x86)\Android\Android sdk\platform tools\adb.exe”-s 69c7aa170104安装“C:\Program Files(x8

    • 问题内容: 我希望更改为在我的Web应用程序中实现无状态Spring Security的目的是结束,但事实并非如此。 进行了此更改后,由于(根据我的假设)Spring安全性在会话中不存储任何内容,并且无法对安全的Web请求进行身份验证,因此Spring安全性似乎无法正常工作。 我如何利用此无状态功能? 我似乎尚未找到任何有关如何为无状态Web应用程序实现无状态Spring安全的示例。 谢谢 ! 问

    • 有人能帮我吗?我是Android系统的新手,我正尝试在AVD中打开应用程序,安装了应用程序,但我得到错误“一个新的会话不能被创建。(原始错误:命令失败:)”,“杀死”:false,“代码”:1,“信号”:null,“origvalue”:“命令失败:”},“sessionid”:null} 谢谢你事先的帮助 尝试只提供Capabilities.SetCapability(“AppActivity”

    • 我正在学习Appium,我无法使用以下功能创建远程会话。虽然>功能在模拟设备上的Appium server本身中工作 线程“main”org.openqa.selenium.sessionNotCreatedException中出现异常:无法创建新的远程会话。原始错误:127.0.0.0.1生成信息:版本:“3.141.59”,修订版:“E82BE7D358”,时间:“2018-11-14T08:

    • 我正试图使用Selenium Grid启动一款新的Chrome浏览器,但最终出现以下错误 无法创建新的远程会话。所需功能=能力[{浏览器名称=chrome,版本=55.0.2,平台=WINDOWS}],所需功能=能力[{}]构建信息:版本:“3.0.1”,修订版本:“1969d75”,时间:“2016-10-18 09:49:13 -0700”系统信息:主机:“PL9710388”,ip:“10.