IBM Support

JR53974: ERROR WHEN TRYING TO PUT BACK MESSAGE INTO MQ FROM ACM CATALOGDATALOADSERVICE CLASS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In IBM InfoSphere Master Data Management Collaboration Server
    11.4.0, when trying to put back message into MQ from ACM
    CatalogDataLoadService class, the following exception is thrown:
    
    [7/29/15 21:31:01:363 IST] 00000044 SystemErr     R
    at
    com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.
    java:1716)
    [7/29/15 21:31:01:363 IST] 00000044 SystemErr     R
    ... 23 more
    [7/29/15 21:31:01:363 IST] 00000044 SystemOut     O   MQ Error
    Message: MQJE001: Completion Code '2', Reason '2540'.
    [7/29/15 21:31:01:363 IST] 00000044 SystemOut     O   Attempt
    to connect to Queue Manager failed.
    [7/29/15 21:31:01:363 IST] 00000044 SystemErr     R
    java.lang. NullPointerException
    [7/29/15 21:31:01:363 IST] 00000044 SystemErr     R
    at com.
    ibm.mdm.integration.utils.MqClient.openQueue(MqClient.java:148)
    [7/29/15 21:31:01:363 IST] 00000044 SystemErr     R
    at com.
    ibm.mdm.integration.utils.MqClient.publishMsgToOutboundQueue(MqC
    lient.java:99)
    [7/29/15 21:31:01:363 IST] 00000044 SystemErr     R           at
    
    In systemErr.log, the following was seen:
    
    
    
    [7/29/15 21:31:01:362 IST] 00000044 SystemErr     R Caused by:
    com.ibm.mq.jmqi.JmqiException: CC=2;RC=2540;AMQ9204:
    Connection to host '172.31.55.137(1414)' rejected.
    [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2540;AMQ9520:
    Channel not defined remotely.
    [2=172.31.55.137(1414),3=MDM.CHANNEL]],3=172.31.55.137(1414),5=R
    emoteConnection.analyseErrorSegment]
    
    
    Cause:
    
    Channel not defined remotely.
    [2=172.31.55.137(1414),3=MDM.CHANNEL
    
    wcs.properties file has this setting:
    wcs.mq.port.num=1415
    
    However, WCSConfiguration.java is reading the property as:
    (wcsProp.getProperty("wcs.mq.port", "1414"))
    
    This leads to the port always being read as 1414, the default
    value and overwriting the value set in the wcs.properties file.
    If the MQ has a different port number which has been configured
    in wcs.properties, that value is not being read, resulting in
    failure of MQ connection.
    

Local fix

  • Manually change the port number in the WCSConfiguration.java to
    read the property as (wcsProp.getProperty("wcs.mq.port",
    "1415"))
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All InfoSphere Master Data Management Collaborative Edition  *
    * implementations are affected by this issue.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In IBM InfoSphere Master Data Management Collaboration       *
    * Server 11.4.0, when trying to put back message into MQ from  *
    * ACM CatalogDataLoadService class, the following exception is *
    * thrown:                                                      *
    * [7/29/15 21:31:01:363 IST] 00000044 SystemErr R at           *
    * com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(Remote *
    * FAP. java:1716) [7/29/15 21:31:01:363 IST] 00000044          *
    * SystemErr R ... 23 more [7/29/15 21:31:01:363 IST] 00000044  *
    * SystemOut O MQ Error Message: MQJE001: Completion Code '2',  *
    * Reason '2540'. [7/29/15 21:31:01:363 IST] 00000044 SystemOut *
    * O Attempt to connect to Queue Manager failed. [7/29/15       *
    * 21:31:01:363 IST] 00000044 SystemErr R java.lang.            *
    * NullPointerException [7/29/15 21:31:01:363 IST] 00000044     *
    * SystemErr R at com.                                          *
    * ibm.mdm.integration.utils.MqClient.openQueue(MqClient.java:1 *
    * 48) [7/29/15 21:31:01:363 IST] 00000044 SystemErr R at com.  *
    * ibm.mdm.integration.utils.MqClient.publishMsgToOutboundQueue *
    * (MqC lient.java:99) [7/29/15 21:31:01:363 IST] 00000044      *
    * SystemErr R at In systemErr.log, the following was seen:     *
    * [7/29/15 21:31:01:362 IST] 00000044 SystemErr R Caused by:   *
    * com.ibm.mq.jmqi.JmqiException: CC=2;RC=2540;AMQ9204:         *
    * Connection to host '172.31.55.137(1414)' rejected.           *
    * [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2540;AMQ9520:       *
    * Channel not defined remotely.                                *
    * [2=172.31.55.137(1414),3=MDM.CHANNEL]],3=172.31.55.137(1414) *
    * ,5=R emoteConnection.analyseErrorSegment]                    *
    * Cause: Channel not defined remotely.                         *
    * [2=172.31.55.137(1414),3=MDM.CHANNEL wcs.properties file has *
    * this setting: wcs.mq.port.num=1415                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Customers facing this issue should apply IBM InfoSphere      *
    * Master Data Management Collaboration Server Version 11.4.0,  *
    * Interim Fix 10 to gain resolution for this problem.          *
    ****************************************************************
    

Problem conclusion

  • This issue was fixed in IBM InfoSphere Master Data Management
    Collaboration Server Version 11.4.0, Interim Fix 10 and is
    available on the IBM Support site.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR53974

  • Reported component name

    MDM SERVER FOR

  • Reported component ID

    5724V5100

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-07-30

  • Closed date

    2015-08-14

  • Last modified date

    2015-08-14

  • 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

    MDM SERVER FOR

  • Fixed component ID

    5724V5100

Applicable component levels

  • RB40 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS2U2U","label":"InfoSphere Master Data Management Collaboration Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.4","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 August 2015