This topic includes the following sections:
Diagnostic tool is a Tuxedo command. It provides a convenient way of collecting Tuxedo runtime information, especially when system administrators analyze problems that can only be reproduced in production environment.
To use diagnostic tool, install the commands listed in the following table, depending on your platform, and set them in environment variable
Diagnostic tool is a Tuxedo command named
Before using the diagnostic tool, manually fill up
diagnoseToolEnvFile file with the following environment variables and put it in
TUXDIR=<Value of Tuxedo Environment Variable TUXDIR>
APPDIR=<Value of Tuxedo Environment Variable APPDIR>
TUXCONFIG=<Value of Tuxedo Environment Variable TUXCONFIG>
BDMCIBFUG=<Value of Tuxedo Environment Variable BDMCONFIG>
DIAGNOSEROOTDIR=<Value of Environment Variable DIAGNOSEROOTDIR>
|Note:||The configuration needs to be done at least one time. All environment variables are indispensable; any configuration change should be manually updated in
diagnosetool --type <error|crash|hang> [--tmtrace] [--aduitlog] [--ubb] [--dmc] [--core <core_path>] [--pid <Process_number>] [--trace <executable_with_option>]
diagnosetool.exe --type <error|crash|hang> [--tmtrace] [--aduitlog] [--ubb] [--dmc] [--core <core_path>] [--pid <Process_number>]
|Note:||For more information about bug type, please see Debug Information.|
There are three problem types.
If a process crashes and generates a core or dump file, you can use diagnostic tool to get the stack trace written on the file. You can define the problem type as "Server or Client Crash" and get the corresponding information.
If a process enters an endless loop or keeps waiting in a function for a long time, you can use diagnostic tool to figure out what the process is doing. You can define the problem type as "Server or Client Hang" and get the corresponding information.
You can get different debug information according to different problem types.
|Note:||Please run diagnostic tool by the same owner during the running process.|
The followings are general information.
|Note:||The information is not supported on Linux systems.|
TMTRACEand get the corresponding
|Note:||This action requires you to shut down those Tuxedo servers. You can choose to do it by yourselves or by the diagnostic tools, or choose not to shut down any server, letting the function to be useless.|
|Note:||The action requires you to shut down
|Note:||The information is supposed to be confidential and you can choose not to provide it.|
|Note:||The information is not supported on Windows platforms.|
|Note:||The information is not supported on Solaris platforms.|
Under product root directory,
log/<year>.<month>.<day>-<hour>.<minute>.<second> sub-directory keeps all debug information and may contain the following files.
|Note:||It is not supported on Windows platforms.|