IBM Support

IT30032: Adding a custom classpath in the service.env file does not work as documented with the IBM MQ Telemetry service.

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

  • The IBM MQ Telemetry service documentation states that a custom
    classpath can be added to the service.env file, which in turn
    allows the use of a login module. However, the classpath is lost
    when the Telemetry service is started, resulting in the login
    module not being being invoked.
    

Local fix

  • Add the CLASSPATH directly in the controlMQXR_mqm.sh script
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ Telemetry service, who
    are using the service.env file to specify a CLASSPATH for a JAAS
    login module that is stored within the IBM MQ installation
    directory.
    
    
    Platforms affected:
    Linux on x86-64, Linux on zSeries, Linux on S390, AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using the IBM MQ Telemetry service, a CLASSPATH can be
    defined in the service.env file to point to an JAAS login module
    that will be invoked when an MQTT client application connects.
    
    If the CLASSPATH in the service.env file was pointing to an IBM
    MQ installation directory (so that the IBM MQ Telemetry service
    could use the sample JAASLoginModule shipped as part of IBM MQ,
    for example), then it would be appended to the CLASSPATH for the
    IBM MQ Telemetry service and then removed before the login
    module could be called.
    

Problem conclusion

  • The IBM MQ Telemetry service has been updated so that the
    CLASSPATH defined within service.env will always be added to the
    IBM MQ Telemetry service CLASSPATH, irrespective of whether the
    path points to an IBM MQ installation directory or not.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.9
    v9.1 CD    9.1.5
    v9.1 LTS   9.1.0.5
    
    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

    IT30032

  • 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

    2019-08-19

  • Closed date

    2019-12-09

  • Last modified date

    2019-12-09

  • 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

[{"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":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
09 December 2019