About Tracing

Server diagnostic tools allow trace information to be sent to either a file or standard output (the "destination").

Note: Traces that are accidentally left switched on can greatly affect server performance. When you encounter performance problems, checking for these is advised.

See Also
About Server Diagnostic Commands
Monitoring Servers
Kill Transaction Command

The following trace information can be sent to either a file or standard output:

  • SQL output
  • MQL trace: program execution, including both tcl and Java program objects
  • VERBOSE trace of client/server dispatches.
  • Server Memory Usage
  • FCS
  • FTP and FTPS communication
  • SMTP communication
  • LDAP communication
  • Trigger execution
  • Workflow debugging
  • Index tracing - to identify queries that could be improved by defining an Index
  • Studio Customization Toolkit calls
  • JPO compilation and classloader messages
  • DesignSync tracing for troubleshooting when implementing a designsync store
  • User-defined trace types
  • searchindex tracing for troubleshooting a particular advanced search indexing process

Tracing for the various 3DSpace kernel operations may be turned on and off using:

  • Environment variables in the server's UNIX startup script or .ini file settings
  • MQL trace command
  • Studio Customization Toolkit logwriter methods

The sections that follow describe how to configure tracing using MQL. Note that these commands can be issued in a server setting via the administration page emxRunMql.jsp, which is accessible to Administrators via the 3DSpace apps' Administration menu.

All types of tracing can also be turned on (and off) using the following MQL commands: 

trace type TYPE{,TYPE} |filename FILENAME | [not full];
                       |on                |
                       |off               |
                       |text STRING       |

The complete syntax and clauses for working with trace are discussed in "trace Command" in the Reference Commands chapter of the MQL Concepts.