IBM Support

IT21125: WebSphere MQ classes for Java trace is written to the console rather than a trace file

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

  • A WebSphere MQ V7.1 classes for Java application connects to a
    queue manager using the BINDINGS transport. In order to collect
    trace from the application, the following steps are performed:
    
    - Bring up a command prompt.
    - Create a com.ibm.mq.commonservices properties file that
    contains the single entry:
    
    Diagnostics.MQ=enabled
    
    This allow the trace to be controlled using the WebSphere MQ
    commands strmqtrc and endmqtrc.
    - Run the command:
    
      strmqtrc -m <queue manager name>
    
    to start queue manager trace on the queue manager that the
    application connects to.
    -Start the application with the following Java command:
    
    java -Djava.library.path=<MQ_INSTALLATION_PATH>\java\lib
    -Dcom.ibm.mq.commonservices=<COM.IBM.MQ.COMMONSERVICES_PROPERTIE
    S_FILE>
    
    When the application starts, messages similar to the ones shown
    below are written to the console, rather than a trace file:
    
    *** WMQ trace not available *** WMQ trace data from ***Unknown
     class/method name (64/103) ***() - WebSphere MQ Trace Monitor
    sleeping for 10 seconds
    *** WMQ trace not available *** WMQ trace data from ***Unknown
    class/method name (64/39) ***() -
    +----------------------------------------------+
    *** WMQ trace not available *** WMQ trace data from ***Unknown
    class/method name (64/39) ***() - |
                                        |
    *** WMQ trace not available *** WMQ trace data from ***Unknown
    class/method name (64/39) ***() - | Plug-in name     :
                     com.ibm.mq.commonservices |
    *** WMQ trace not available *** WMQ trace data from ***Unknown
     class/method name (64/39) ***() - |
                                        |
    *** WMQ trace not available *** WMQ trace data from ***Unknown
    class/method name (64/39) ***() -
    +----------------------------------------------+
    *** WMQ trace not available *** WMQ trace exit from ***Unknown
    class/method name (64/39) ***()
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ V7.1 classes for
    Java who:
    
    - Have applications that connect to a queue manager using the
    BINDINGS transport.
    - And have been requested to collect a trace of the application
    by IBM Support.
    - And are attempting to collect the trace using the WebSphere MQ
    facilities, using a com.ibm.mq.commonservices properties file
    containing the entry
    
        Diagnostics.MQ=enabled
    
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using the WebSphere MQ V7.1 classes for Java, trace can be
    collected using either the WebSphere MQ common services trace
    facility or the WebSphere MQ messaging client trace mechanism.
    
    The WebSphere MQ common services trace mechanism can be
    configured to collect information using WebSphere MQ facilities
    or WebSphere MQ Java facilities. WebSphere MQ facilities is
    supported for WebSphere MQ classes for Java applications that
    connect to a queue manager using the BINDINGS transport, and
    allows trace to be controlled by the strmqtrc and endmqtrc
    commands.
    
    It should also have resulted in trace information being
    collected using the queue manager trace mechanism. and written
    to the queue manager trace files.  However, the trace output was
    written to the standard output stream rather than a trace file.
    

Problem conclusion

  • The WebSphere MQ V7.1 classes for Java have been updated so that
    if a WebSphere MQ classes for Java application, which connects
    to a queue manager using the BINDINGS transport, is started
    using a Java command with the following format:
    
    java -DDiagnostics.MQ=enabled
    -Djava.library.path=MQ_INSTALLATION_PATH/java/lib;MQ_INSTALLATIO
    N_PATH/bin MyApp
    
    then the WebSphere MQ classes for Java will collect trace
    information using WebSphere MQ facilities. This will result in
    the trace appearing in a queue manager trace file.
    
    Note that the Java system property -Djava.library.path needs to
    be set to the values shown above. This allows the WebSphere MQ
    classes for Java to load the libraries required to use WebSphere
    MQ facilities.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.9
    
    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

    IT21125

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-21

  • Closed date

    2017-09-29

  • Last modified date

    2017-09-29

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

  • Fixed component ID

    5724H7220

Applicable component levels

  • R710 PSY

       UP



Document information

More support for: WebSphere MQ
APAR / Maintenance

Software version: 710

Reference #: IT21125

Modified date: 29 September 2017


Translate this page: