IBM Support

IV28666: THE WEBSPHERE MQ JMS MESSAGE PROPERTY JMSXUSERID IS PADDED WITH BLANKS RESULTING IN AUTHORIZATION PROBLEMS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The JMSXUserID property is mapped to the same value as
    the UserIdentifier field in the MQMD, which is precisely 12
    characters in length.
    
    Currently additional padding is added to the end of the
    JMSXUserID for IDs less than 12 characters.
    Some applications may have trouble correctly interpreting
    the padded characters resulting in authorization failures.
    

Local fix

  • The application can issue the String.trim() method before the
    authentication occurs to remove the extra padding.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7 classes for Java.
    - The WebSphere MQ V7 classes for JMS.
    - The WebSphere MQ V7 Resource Adapter.
    - The WebSphere MQ V7 OSGi bundles.
    - The WebSphere Application Server V7 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8.5 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V6.1 WebSphere MQ messaging
    provider who have configured the WebSphere variable
    MQ_INSTALL_ROOT to point to a WebSphere MQ V7 installation.
    
    who use the JMSXUserID message property.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    The WebSphere MQ classes for JMS will always ensure that the
    JMSXUserID property is exactly 12 characters in length.
    
    While mapping JMS fields onto WebSphere MQ header fields of
    incoming message, JMSXUserID property is set to the same value
    as the 'UserIdentifier' field in MQMD. The UserIdentifier field
    has a fixed length of 12 characters. When the WebSphere MQ
    classes for JMS copy the information from the UserIdentifier
    field into the JMXUserID, the length is preserved.
    
    If the size of JMSXUserID is less than the 12 char, the client
    pads the JMSXUserID with blank spaces to make it 12 characters
    in length. Some third party applications do not expect the
    JMSXUserID to be padded in this way.
    

Problem conclusion

  • The fix provides a new configuration property that for the
    WebSphere MQ classes for JMS. This property is
    named: "com.ibm.mq.jms.trimJMSXUserID" and can be set to a
    boolean value. The value 'true' will prevent the padding of
    JMSXUserID with blank spaces.
    
    For example:
    java -Dcom.ibm.mq.jms.trimJMSXUserID=true MyProgram
    Here MyProgram has to be replaced with main class of the java
    application.
    
    The default value of this property is false, which will cause
    the JMSXUserID to be padded with whitespace to a length of 12
    characters.
    
    
    
    Like other configuration properties for the WebSphere MQ classes
    for JMS, this property can be set as a Java System Property on
    the command line (e.g java -
    Dcom.ibm.mq.jms.trimJMSXUserID=true).
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.10
    --------           --------------------
    Windows            U200352
    AIX                U853055
    HP-UX (PA-RISC)    U853082
    HP-UX (Itanium)    U853087
    Solaris (SPARC)    U853083
    Solaris (x86-64)   U853089
    iSeries            7.0.1.10
    Linux (x86)        U853084
    Linux (x86-64)     U853088
    Linux (zSeries)    U853085
    Linux (Power)      U853086
    zOS                7.0.1.10
    
                       v7.1
    Platform           Fix Pack 7.1.0.3
    --------           --------------------
    Windows            7.1.0.3
    AIX                7.1.0.3
    HP-UX (Itanium)    7.1.0.3
    Solaris (SPARC)    7.1.0.3
    Solaris (x86-64)   7.1.0.3
    iSeries            7.1.0.3
    Linux (x86)        7.1.0.3
    Linux (x86-64)     7.1.0.3
    Linux (zSeries)    7.1.0.3
    Linux (Power)      7.1.0.3
    zOS                7.1.0.3
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.1
    
    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

    IV28666

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-25

  • Closed date

    2012-12-12

  • Last modified date

    2012-12-12

  • 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 AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R701 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]

Document Information

Modified date:
01 October 2021