Diagnostic log files

Additional files are created when certain events occur with the Launcher:

• If an unhandled system exception occurs in a map thread that is running, troubleshooting information for technical support purposes is written to a file named GPFThreadId-TimeStamp.txt on Windows and ABORT-pid.txt on UNIX. You can find this diagnostic log file in the installation directory of WebSphere® Transformation Extender.
• The dtxAbort.log file is a UNIX environment-specific log file that indicates when the Launcher, Command Server, Platform API, or Java™ API is attempting to acquire memory from the operating system but does not succeed.

  The dtxAbort.log file gets created in $DTX_TMP_DIR when the respective application is started. $DTX_TMP_DIR is normally empty, which indicates that there has not been a failed attempt to get additional memory.

  If a failure occurs while attempting to obtain additional memory, the message appended to the dtxAbort.log file will be similar to one of the following messages:

  • Fatal Error: malloc() - Unable to Retrieve Additional New Memory.
  • Fatal Error: realloc() - Unable to Retrieve Additional New Memory.

    The message is prefaced with text indicating the date and time that the failure occurred.