Date Created: Tue 08-Sep-2009

Related Document Categories:


    Web Application times out, and logs show JMS error Reason 2195

    The stack trace below was caused by a MainFrame MQ Listener port being taken over by another monitoring port, so when we tried to telnet to the port all was ok.

    So it was not a connectivity issue as first we thought. After deep investigation we opted to restart the MQ listener and it would not come up due to port conflict.

    The Reason code was unexpected error as everything looked fine as far as WebSphere MQ JARS were concerned because they could connect to he correct location (destination) but could not actually get to the QM and since the another program on the MainFrame was using the port WMQ in WAS was sort of responding but not properly hence error was not a typical error


    Log: Of System Out.

    [9/7/09 15:43:27:620 CEST] 00000033 Z com.<custom_class>.framework.audit.jms.JMSAuditMessenger newInstance Failed to audit message, could not open JMS Connection. ${caus
    e.message} MESSAGE FORMAT ERRORS OCCURED FOR TEMPLATE: "Failed to audit message, could not open JMS Connection. ${cause.message}" Failed to find value for parameter: cause.message; available params are {thread=WebContainer : 0}
    javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<Queue Manager Host:Queue Manager Name>
    at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:644)
    at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2505)
    at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1850)
    at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:161)
    at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:202)
    at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:121)
    at com.ibm.mq.jms.MQQueueConnectionFactory.createConnection(MQQueueConnectionFactory.java:1038)
    at com.ibm.ejs.jms.JMSManagedConnection.createConnection(JMSManagedConnection.java:1435)
    at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:315)
    at com.ibm.ejs.jms.JMSManagedConnectionFactory.createUnifiedManagedConnection(JMSManagedConnectionFactory.java:1262)
    at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:622)
    at com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1895)
    at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java:1570)
    at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2338)
    at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:915)
    at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:605)
    at com.ibm.ejs.jms.JMSConnectionFactoryHandle.createConnection(JMSConnectionFactoryHandle.java:248)
    at com.<custom_class>.framework.audit.jms.JMSAuditMessenger.initConnection(JMSAuditMessenger.java:98)
    at com.<custom_class>.framework.audit.jms.JMSAuditMessenger.newInstance(JMSAuditMessenger.java:74)
    at com.<custom_class>.framework.audit.AuditMessengerFactory.newAuditMessenger(AuditMessengerFactory.java:43)
    at com.<custom_class>.<sub_class>.messagingservice.processing.AuditProcessor.performStep(AuditProcessor.java:156)
    at com.<custom_class>.<sub_class>.messagingservice.processing.ProcessHandler.performAudit(ProcessHandler.java:157)
    at com.<custom_class>.<sub_class>.messagingservice.processing.ProcessHandler.processMsg(ProcessHandler.java:127)
    at com.<custom_class>.<sub_class>.messagingservice.ejb.MessagingServiceSoapBindingImpl.sendReceive(MessagingServiceSoapBindingImpl.java:173)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:618)
    at com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.invokeMethod(JavaDispatcher.java:178)
    at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invokeMethod(J2ee14EJBDispatcher.java:173)
    at com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.invokeOperation(JavaDispatcher.java:141)
    at com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.processRequestResponse(SoapRPCProcessor.java:464)
    at com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.processMessage(SoapRPCProcessor.java:425)
    at com.ibm.ws.webservices.engine.dispatchers.BasicDispatcher.processMessage(BasicDispatcher.java:134)
    at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invoke(J2ee14EJBDispatcher.java:154)
    at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
    at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invoke(JAXRPCHandler.java:147)
    at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:64)
    at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
    at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
    at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
    at com.ibm.ws.webservices.engine.transport.http.WebServicesServlet.doPost(WebServicesServlet.java:840)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at com.ibm.ws.webservices.engine.transport.http.WebServicesServletBase.service(WebServicesServletBase.java:341)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:591)
    at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3453)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
    at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
    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:136)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
    ---- Begin backtrace for Nested Throwables
    com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2195
    MQJE018: Protocol error - unexpected segment type received

Middleware Mentor - Steven Charles Robinson

About Me

Steve Robinson has been working in IT for over 15 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware consulting. Steve comes from both an administration and development background.

Before moving to JEE, Steve was an accomplished developer and consultant for both IBM Lotus Notes and Microsoft .NET Technologies.

Follow Steve as @stevencrobinson on twitter.

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Oracle WebLogic Categories

JBoss Categories

Other Categories