Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Dec 21, 2023

Display QMGR name in JMS error messages

Our JMS Queue Connection Factory in WAS is configured with the Queue Sharing Group name and also with a VIPA IP and Port.
In practice, the connection can be established with any QMGR in the QSG environment.
This is very good in terms of High Availability, but give us a challenge when we receive any kind of error from the MQ.

For example, in the RC 2540, there is no indication of what QMGR responded this error. The following messages are logged in the WAS logs:

JMSWMQ0018: Failed to connect to queue manager 'QSG1' with connection mode 'Client' and host name ''.

JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2540' ('MQRC_UNKNOWN_CHANNEL_NAME'). CC=2;RC=2540;AMQ9520: Channel not defined remotely. í3=MQA3.TEST.SVRCONNù

This happens with other MQRC messges too.

It would be nice if we have any indication of what QMGR responded the error to WebSphere Application Server.

Thanks in advance!

Idea priority Medium
  • Admin
    Matthew Leming
    Mar 19, 2024

    If JMS successfully connects to a queue sharing group then it will use the resolved queue manager name in any subsequent error messages.
    However if the connection isn't successfully made, and this includes the case when the channel name is unknown, then the JMS code won't know the queue manager name and instead will use the queue sharing group name.
    I'm afraid there is no way to change that without a redesign of the MQ wire protocol.
    As a result we are declining this idea. While declined the idea can still be voted, and commented, upon.