IBM Support

IT19911: MINOR JMS PERFORMANCE ISSUE WHEN SENDING MANY MESSAGES ENCODED USING JAVA CHARSET NAME

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

  • After upgrading an IBM MQ classes for JMS application from using
    a V8 client to a V9 client, a minor degradation in performance
    was observed when sending many JMS TextMessages that have the
    JMS_IBM_CHARACTER_SET property set on them with a value that is
    the name of a Java character set.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ V9 classes for JMS who
    send many JMS TextMessages in quick succession where each
    message has the JMS_IBM_CHARACTER_SET property configured to a
    Java character set name.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When sending a JMS TextMessage that had the:
    
      JMS_IBM_CHARACTER_SET
    
    message property configured, the MQ classes for JMS attempted to
    determine whether the value of the property was a numerical
    String value that represented a coded character set identifier
    (CCSID), for example "1208", or a Java character set name, for
    example "UTF-8".  The MQ classes for JMS attempted to do this by
    parsing the value as an integer number and if successful, treat
    the value as a CCSID number to encode the body of the JMS
    TextMessage.  If the value could not be parsed as an integer
    number, then a java.lang.NumberFormatException was caught and
    the value treated as a Java character set name.
    
    The process required to generate the
    java.lang.NumberFormatException was sufficiently great to cause
    a degradation in performance when sending many JMS TextMessages
    in quick succession.
    

Problem conclusion

  • The MQ classes for JMS have been updated to avoid parsing the
    value of the:
    
      JMS_IBM_CHARACTER_SET
    
    message property as an integer and thus preventing the expensive
    generation of a java.lang.NumberFormatException.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    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

    IT19911

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-28

  • Closed date

    2017-05-30

  • Last modified date

    2017-05-30

  • 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

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 May 2017