IBM Support

IT31166: JMS FDC generated when bad file path is specified for the property "com.ibm.msg.client.commonservices.trace.outputName"

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

  • If an invalid output file path is specified in the following
    trace property:
    
      com.ibm.msg.client.commonservices.trace.outputName
    
    then trace is redirected to the System.err stream as expected.
     However a JMS FFDC file is also generated if the file path is
    invalid due to being unable to create a directory.
    
    For example, the following command syntax will result in the
    FFDC file being created if the user running the command does not
    have write access to the /opt directory:
    
    java
    
    -Dcom.ibm.msg.client.commonservices.trace.outputName=/opt/newDir
    ectory/trace.trc
      -Dcom.ibm.msg.client.commonservices.trace.status=ON
      -cp .;jms.jar:com.ibm.mq.allclient.jar MyTestApp
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ classes for Java/JMS API
    who are attempting to enable trace for their client application,
    and are also specifying a path for the trace file output
    location that would require a new directory to be created.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    One mechanism to enable trace of the IBM MQ classes for
    Java/JMS, where the trace is directed to a specified file
    location, is to start the JVM with the following arguments:
    
      -Dcom.ibm.msg.client.commonservices.trace.status=ON
    
    -Dcom.ibm.msg.client.commonservices.trace.outputName="traceOutpu
    tName"
    
    
    If a trace output location is specified such that a new
    directory needs to be created, for example:
    
      -Dcom.ibm.msg.client.commonservices.trace.status=ON
    
    -Dcom.ibm.msg.client.commonservices.trace.outputName="/new/direc
    toryPath/trace.trc"
    
    then there is the possibility that the specified new directory
    cannot be created (in the case of permission denied for
    example). In this event, trace is redirected to the standard
    error stream (STDERR), with a message directed to the standard
    out stream (STDOUT) of the form:
    
    "The IBM MQ messaging client trace mechanism could not
    initialize the trace file 'location.trc' due to the exception
    'java.io.IOException: The IBM MQ messaging client trace
    mechanism does not have permission to
    write to the trace file '/new/directoryPath/location.trc' in the
    directory '/new/directoryPath''. Trace will be written to
    System.Err."
    
    However, unlike other types of JMS trace error (e.g. being
    unable to create the trace file for example), an FDC would also
    be generated if the directory could not be created. Hence, the
    error where a new directory cannot be created was inconsistent
    in its behaviour when compared to other types of JMS trace
    errors.
    

Problem conclusion

  • If a specified new directory cannot be created as part of the
    trace output location, an FDC file will no longer be generated.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.15
    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

    IT31166

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-12-04

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

  • 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 MP

  • Fixed component ID

    5724H7251

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

Document Information

Modified date:
16 January 2020