IBM Support

IT11880: BOOLEAN PROPERTIES IN JAVA PROPERTY STORE ALWAYS TREATED AS FALSE IF THE VALUE HAS TRAILING SPACES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the IBM MQ classes for JMS or the IBM MQ classes for
    Java and reading properties in from a java configuration file,
    boolean and long properties are not set to the expected value if
    the configuration file contains a trailing space after the value
    of the property.
    
    For example
    	"exampleProperty=true "
    results in the exampleProperty being set to false.
    	
    and
    	"anotherProperty=123 "
    results in anotherProperty being set to the default long value
    for the property store.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ classes for JMS or the
    IBM MQ classes for Java who are reading System properties from a
    java configuration file, and who are using boolean or long
    properties with trailing spaces after the value of the property.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When reading System properties or properties from a
    configuration file into the IBM MQ classes for JMS or the IBM MQ
    classes for Java property store, all properties are read as
    Strings, with no implicit type. When a non-String property is
    retrieved from the property store, the String value is converted
    into a value of the correct type. The String values read from
    the property store were not being trimmed of whitespace before
    the conversion to a boolean or long value was attempted.  In the
    case of a boolean property, if the property was set to anything
    other than "true" then the final value was set to be false.  In
    the case of a long property, then the trailing spaces caused a
    NumberFormatException which was caught by the  IBM MQ classes
    for JMS or the IBM MQ classes for Java code, and the property
    was then set to the default long value for the property store.
    

Problem conclusion

  • The logic of the property store parsing code has been updated to
    remove trailing spaces when properties are read from a file
    before the String values read in are parsed into boolean or long
    properties.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.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

    IT11880

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-21

  • Closed date

    2016-05-25

  • Last modified date

    2016-05-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

    5724H7251

Applicable component levels

  • R800 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":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 May 2016