IBM Support

IT34512: UNABLE TO PUBLISH JMS RETAINED PUBLICATIONS FROM JMSOUTPUT NODE WITH JMS PROVIDER WEBSPHERE MQ

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

  • A JMSOutput node is used to publish a JMS Topic as a retained
    publication, where the JMS provider is WebSphere MQ.
    
    A JMS application property called 'JMS_IBM_Retain' with a value
    '1' is created in the JMS application properties section of the
    message tree using a JMSHeader Node , ahead of the JMSOutput
    node.
    
    However, the JMSHeader node writes the application property
    'JMS_IBM_Retain' to the message tree as a character value,
    instead of the integer value required by MQ JMS.
    
    The publication fails in the JMSOutput node because WebSphere MQ
    rejects the data type of the application property. The following
    IBM Integration Bus error is seen in the logs:
    
    BIP4662E: ( MN10.SRV1 ) IIB JMSClient. ''Broker <Node Name>';
    Execution Group <Server Name>; Message Flow <Flow Name>; Node
    'ComIbmJMSClientOutputNode::JMSOUT::ComIbmJMSClientOutputNode'
    '' There was a problem setting JMS related header data to the
    JMS output message. [02/11/2020 17:06:59]
    
    In the product's service trace the following WebSphere MQ error
    text may be seen:
    
    Node 'ComIbmJMSClientOutputNode::JMS
    Output::ComIbmJMSClientOutputNode' ) ) (Insert=(Type=5) (Text=
    JMSCC0051: The property 'JMS_IBM_Retain' should be set using
    type 'java.lang.Integer',
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 and IBM App Connect
    Enterprise version 11 using the JMSHeader and JMSOutput nodes to
    publish retained JMS publications using MQ JMS Client.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A JMSOutput node is used to publish a JMS Topic as a retained
    publication, where the JMS provider is WebSphere MQ.
    
    A JMS application property called 'JMS_IBM_Retain' with a value
    '1' is created in the JMS application properties section of the
    message tree using a JMSHeader Node , ahead of the JMSOutput
    node.
    
    However, the JMSHeader node writes the application property
    'JMS_IBM_Retain' to the message tree as a character value,
    instead of the integer value required by MQ JMS.
    
    The publication fails in the JMSOutput node because WebSphere MQ
    rejects the data type of the application property. The following
    IBM Integration Bus error is seen in the logs:
    
    BIP4662E: ( MN10.SRV1 ) IIB JMSClient. ''Broker <Node Name>';
    Execution Group <Server Name>; Message Flow <Flow Name>; Node
    'ComIbmJMSClientOutputNode::JMSOUT::ComIbmJMSClientOutputNode'
    '' There was a problem setting JMS related header data to the
    JMS output message. [02/11/2020 17:06:59]
    
    In the product's service trace the following WebSphere MQ error
    text may be seen:
    
    Node 'ComIbmJMSClientOutputNode::JMS
    Output::ComIbmJMSClientOutputNode' ) ) (Insert=(Type=5) (Text=
    JMSCC0051: The property 'JMS_IBM_Retain' should be set using
    type 'java.lang.Integer',
    

Problem conclusion

  • The product now correctly sets an Integer value for the JMS
    provider property "JMS_IBM_Retain" when publishing a JMS Topic
    using the MQ JMS Client. This enables the the JMS topic to be
    retained in the MQ JMS Server for a JMS subscriber application
    to later consume.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.24
    v11.0      11.0.0.12
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34512

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-03

  • Closed date

    2021-03-22

  • Last modified date

    2021-03-22

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
23 March 2021