Mq Protocol Error
AND AMQ9213 AT THE CLIENT WHEN A JMS SESSION IS SHARED BY MULTIPLE THREADS Fixes are available Fix Pack 7.1.0.6 for WebSphere MQ V7.1 8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 8.5.5.7: WebSphere amq9504: a protocol error was detected for channel Application Server V8.5.5 Fix Pack 7 8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 8.5.5.9: the failure type was 11 with associated data of 0. WebSphere Application Server V8.5.5 Fix Pack 9 8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 Subscribe You can track all active APARs rm557001 for this component. APAR status Closed as program error. Error description The queue manager reports an AMQ9504 protocol error when a JMS QueueSession is shared between multiple threads. From one thread an MQDISC call arrives at the queue manager and ends the conversation while at approximately the same time that JMS QueueSession is used to send an internal spiNotify call request on another QueueReceiver from a different thread. AMQ9213 is returned by the JMS Client. Local fix Problem summary **************************************************************** USERS AFFECTED: This issue affects users of: - The WebSphere MQ V7.1 classes for JMS. - The WebSphere MQ V7.1 resource adapter. - The WebSphere MQ V7.5 classes for JMS. - The WebSphere MQ V7.5 resource adapter. - The WebSphere Application Server V8.5 WebSphere MQ messaging provider. who have multi-threaded applications that connect to a WebSphere MQ queue manager using WebSphere MQ messaging provider normal mode using the CLIENT transport and: - Create a JMS Session, and a JMS MessageConsumer from the JMS Session, on one thread. - Close the JMS Session from a different thread to the one that is using it. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When an application creates a JMS session, a connection handle (hconn) is assigned to the JMS session and is used whenever the JMS session communicates with the queue manager. If a WebSphere MQ API call needs to be sent to the queue manager, the WebSphere MQ classes for JMS obtain a Call Lock on the connection handle, issue the call and then release the Call Lock. The use of the Call Lock prevents multiple WebSphere MQ API calls being made on the same connection handle at the same time. This means that when a JMS session is closed, the WebSphere MQ classes for JMS will: - Get the Call Lock for the connection handle associated with the JMS Session. - Flow an MQDISC call to the queue manager using the connection handle. - When the MQDISC call completes, release the Call Lock.
MQ V7.1 QMGR GETS AMQ9504 PROTOCOL ERROR; FDC HAS PROBE IDS RM680037 RM039000 A fix is available Fix Pack 7.1.0.4 for WebSphere MQ V7.1 Subscribe You can track all active APARs for this component. APAR status Closed as unreproducible in next release. Error description A WebSphere MQ V7.0.0.0 Java client application connecting to an MQ v7.1 queue manager receives AMQ9504: protocol error. An FDC is created with Probe IDs RM680037 and RM039000. WebSphere MQ First Failure Symptom Report ========================================= Probe Id :- RM680037 Component :- rriBadDataReceived Program Name :- http://www.ibm.com/support/docview.wss?uid=swg1IV57472 amqrmppa Major Errorcode :- rrcE_PROTOCOL_ERROR Probe Description :- AMQ9504: A protocol error was detected for channel -------------------------------------------------------------- MQM Function Stack ccxResponder rrxResponder ccxReceiveThreadFn cciProcessOne cciProcessUserData cciProcessAsyncRcv rriServerAsyncRcv rriMQIServerReceive rriConvertValidate rriBadDataReceived xcsFFST WebSphere MQ First Failure Symptom Report ====================================== Probe Id :- RM039000 Component :- rriConvertValidate Program Name :- amqrmppa Major Errorcode :- rrcE_PROTOCOL_ERROR Probe Type :- MSGAMQ9504 Probe Severity :- 2 Probe Description http://www-01.ibm.com/support/docview.wss?uid=swg1IV36766 :- AMQ9504: A protocol error was detected for channel 'Data conversion failed.'. Comment1 :- Data conversion failed. --------------------------------------------------------------- MQM Function Stack ccxResponder rrxResponder ccxReceiveThreadFn cciProcessOne cciProcessUserData cciProcessAsyncRcv rriServerAsyncRcv rriMQIServerReceive rriConvertValidate xcsFFST . Additional symptoms: 2009 RC2009 CC=2 RC=2009 Local fix Upgrade WebSphere MQ client being used for JMS application to 7.0.1.0 or later. Problem summary **************************************************************** USERS AFFECTED: Users of v7.0.0.0 Java clients connecting to a v7.1 or v7.5 queue manager may be affected by this problem. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: A bug existed in the v7.0.0.0 JMS client flow which was fixed in later versions of the code. On queue managers earlier than v7.1, the invalid flow was not detected. Code was added in v7.1 to detect and report the invalid flow and this detection resulted in the rrcE_PROTOCOL_ERROR FDCs being produced. Problem conclusion It is correct behavior for the queue manager to report the invalid flow so this code change was not reverted. The recommended solution for the problem is to upgrade any client still at v7.0.0.0 to a later releae, as Client releases at v7.0.1.0 or later co
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://stackoverflow.com/questions/14609511/amq9504-a-protocol-error-was-detected-for-channel Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up AMQ9504: A protocol error was detected for channel up vote 2 down vote favorite 1 I'm unable to connect remotely from WebSphere protocol error Application Server with Queue Manager at WebSphere MQ. Anyhow it get connected to Queue Manager from WAS that is installed on same machine. I'm using version 7.5 of WebSphere MQ and version 7.0 of WebSphere Application Server. While attempting to connect WAS remotely to Queue Manager following error messages were logged. Error Message from WebSphere MQ: 1/30/2013 21:12:09 - Process(3624.6) User(MUSR_MQADMIN) Program(amqrmppa.exe) Host(KHILT-269) Installation(Installation1) VRMF(7.5.0.0) QMgr(QM.TEST) AMQ9504: A protocol error was detected for channel mq protocol error 'TEST_CHANNEL'. EXPLANATION: During communications with the remote queue manager, the channel program detected a protocol error. The failure type was 11 with associated data of 0. ACTION: Contact the systems administrator who should examine the error logs to determine the cause of the failure. Error Message at WebSphere Application Server: A connection could not be made to WebSphere MQ for the following reason: CC=2;RC=2009 As it can be seen from logs, I have created Queue Manager as QM.TEST and channel as TEST_CHANNEL. The listener port defined for the Queue Manager is 1417 along with protocol TCP. I did lot of google but didn't find any appropriate solution. I appreciate any help in this regard. Thanks in adv, KAmeer websphere-mq websphere-7 share|improve this question edited Jan 31 '13 at 8:10 asked Jan 30 '13 at 16:59 KAmeer 1113 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote I had a similar issue where I have WAS 7 and WMQ 7.5. I was able to make a connection to my existing WMQ 7.0 QM but not my new WMQ 7.5 QM. Apparently there was a change to the WMQ components bundled with WAS 7 after the initial release 7.0.0.0. After updating the resource adapter I was able to make a successfull connection to both queue managers. sh