IBM Support

IC93267: CC=2;RC=2540; AMQ9520: CHANNEL NOT DEFINED REMOTELY MESSAGE IS INCORRECTLY REPORTED FOR BINDINGS TRANSPORT.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If an an application is using the PCFMessageAgent constructor
    PCFMessageAgent(String, int, String) to connect to a queue
    manager and the client transport fails for some reason,
    an exception is thrown with the message:
    
    MQJE001: Completion Code '2', Reason '2540'.
    com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason
    '2540'.
    at
    com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.
    java:247)
    at
    com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedCon
    nection(MQClientManagedConnectionFactoryJ11.java:588)
    at
    com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConn
    ection(MQClientManagedConnectionFactoryJ11.java:630)
    ........
    Caused by: com.ibm.mq.jmqi.JmqiException:
    CC=2;RC=2540;AMQ9204: Connection to host 'localhost(1414)'
    rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2540;AMQ9520:
    Channel not defined remotely.
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:
    2053)
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:
    1226)
    ........
    Caused by: com.ibm.mq.jmqi.JmqiException:
    CC=2;RC=2540;AMQ9520: Channel not defined remotely.
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.analyseErrorSegment
    (RemoteConnection.java:3839)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.receiveTSH(RemoteCo
    nnection.java:2746)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.initSess(RemoteConn
    ection.java:1034)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.connect(RemoteConne
    ction.java:727)
    ........
    
    If the same application, after the getting the exception,
    creates a new
    PCFMessageAgent using the constructor
    PCFMessageAgent(String) to connect to a queue manager using
    bindings transport and this connection also fails, the same
    exception as the client transport is
    thrown with the message containing:
    
    MQJE001: Completion Code '2', Reason '2058'.
    com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason
    '2058'.
    at
    com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.
    java:247)
    at
    com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedC
    onnection(MQBindingsManagedConnectionFactoryJ11.java:259)
    at
    com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedCo
    nnection(MQBindingsManagedConnectionFactoryJ11.java:315)
    ........
    Caused by: com.ibm.mq.jmqi.JmqiException:
    CC=2;RC=2540;AMQ9204: Connection to host 'localhost(1414)'
    rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2540;AMQ9520:
    Channel not defined remotely.
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:
    2053)
    at
    com.ibm.mq.jmqi.remote.api.RemoteFAP.jmqiConnect(RemoteFAP.java:
    1226)
    ........
    Caused by: com.ibm.mq.jmqi.JmqiException:
    CC=2;RC=2540;AMQ9520: Channel not defined remotely.
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.analyseErrorSegment
    (RemoteConnection.java:3839)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.receiveTSH(RemoteCo
    nnection.java:2746)
    at
    com.ibm.mq.jmqi.remote.impl.RemoteConnection.initSess(RemoteConn
    ection.java:1034)
    ........
    
    This exception is incorrect for bindings transport.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ V7.5 classes for Java
    who have applications that construct a PCFMessageAgent.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    An application used the PCFMessageAgent constructor to connect
    to a queue manager using client transport. If the connection
    to the queue manager could not be made (e.g. due to incorrect
    configurations), an exception was thrown and stored in an
    internal variable.
    
    When the application then used the same PCFMessageAgent to
    connect to a queue manager with the bindings transport and the
    connection failed, the exception that was stored previously
    was incorrectly re-thrown.
    

Problem conclusion

  • The WebSphere MQ classes for Java have been modified such that
    the cached exception for the failed client connection is not
    re-thrown when using a bindings-mode connection.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
    Version            v7.5
    --------           --------------------
    Fix available in:  7.5.0.3
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC93267

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-06-20

  • Closed date

    2013-07-31

  • Last modified date

    2013-07-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

  • R750 PSY

       UP



Document information

More support for: WebSphere MQ
APAR / Maintenance

Software version: 7.5

Reference #: IC93267

Modified date: 31 July 2013