Important Notes About Tracing and Troubleshooting Waveset

Before you start tracing or troubleshooting Waveset, note the following:

• Tracing affects system performance. To ensure optimal performance, use the minimum tracing level needed or turn off tracing after debugging the systems.

• Do not enable tracing for the com.waveset class. The com.waveset class is verbose and has many classes, so tracing this class might cause your server to hang.

• Do not configure Waveset to trace at the advanced level unless instructed to do so by Oracle Support.

• If you set exception.trace in the Waveset.properties file to debug a specific problem, do not use it for an extended period of time and be sure you disable it after debugging. Setting exception.trace in the Waveset.properties file can significantly affect system performance.

• By default, Waveset returns stack trace information as HTML comments when certain errors occur. Generally, a stack trace is not visible to the end-user, but the trace can be seen by viewing the page source in the browser.

  Stack trace information can be very useful when diagnosing a problem, but exposes information about the execution of the web application that could be considered a security risk. Production deployments should consider turning off stack trace information rendering by configuring the following setting in Waveset.properties:

  ui.web.disableStackTraceComments=true

  You must perform this change manually on each Waveset server.

  ---

  Note –

  Beginning with Waveset version 8.1.1, the default setting for ui.web.disableStackTraceComments is true. In previous releases, the default setting for ui.web.disableStackTraceComments was false.

  However, because version 8.1.1 is an upgrade and not an install, the new setting does not automatically take place because Waveset.properties is not overridden during an upgrade.

  ---