Home

 

Java trace and FFDC files

 

When Java™ trace is generated for the WebSphere MQ Explorer or for WebSphere MQ Transport for SOAP it is written to a file with a name of the format AMQ.diagid.counter.TRC where diagid is the value of the system property com.ibm.mq.commonservices.diagid associated with this Java process, as described earlier in this section, and counter is an integer greater than or equal to 0. All letters in the name are in upper case. This matches the naming convention used for normal WebSphere MQ trace.

If com.ibm.mq.commonservices.diagid is not specified, the value of diagid is the current time, in the format YYYYMMDDhhmmssmmm.

The WebSphere MQ Java classes trace file has a name based on the equivalent WebSphere MQ Explorer or SOAP Java trace file. The name differs in that it has the string .JC added before the .TRC string, giving a format of AMQ.diagid.counter.JC.TRC.

When Java FFDC is generated for the WebSphere MQ Explorer or for WebSphere MQ Transport for SOAP it is written to a file with a name of the format AMQ.diagid.counter.FDC where diagid and counter are as described for Java trace files.

Java error message output for the WebSphere MQ Explorer and for WebSphere MQ Transport for SOAP is written to the file specified by Diagnostics.Java.Errors.Destination.Filename for the appropriate Java process. The format of these files matches closely the format of the standard WebSphere MQ error logs.

When a process is writing trace information to a file, it appends to a single trace output file for the lifetime of the process. Similarly, a single FFDC output file is used for the lifetime of a process.

All trace output is in the UTF-8 character set.

Note that none of the above applies to output of FFDC data or error messages for the WebSphere MQ Java classes. This occurs as part of exception logging as detailed in WebSphere MQ Using Java. The WebSphere MQ Java class trace is also detailed in WebSphere MQ Using Java.

 

Parent topic:

Java diagnostics

fa15480_

 

Home