How do I Enable Tracing for Load Balancing?

Pramati Server provides a tracing mechanism whereby developers can troubleshoot or debug problems that may occur while using load balancing with the WebGate.

When the plugin is started with enhanced LB enabled, messages produced by the loadbalancer are present in <PluginInstallationHome>/ApachePlugin1.3.log or <PluginInstallationHome>/ ApachePlugin2.0.log file. The log file with property LogFileName generates logging information generated by the plugin alone.

By default, only messages that are marked severe are logged. Pramati Server provides a trace.props file that enables logging. This file should be available in the plugin home. The following is a sample trace.props file:

#~~~~~~~~~ #Trace.props #~~~~~~~~~ handlers=custom_handler handler.custom_handler.type=console handler.custom_handler.details= handler.custom_handler.isAbsolutePath=true handler.custom_handler.appendIfFileExists=true handler.custom_handler.loglevel=all handler.custom_handler.contexttype.packages=.,true; enable.debug=true

Table 1: Trace Properties

Property Description

handlers This is a place holder for the kind of handlers. There can be a number of handlers available doing various types of tracing. Here the entry custom_handler provides the reference to the current handler.

handler.custom_handler.type Tracing can happen either to a file or to the Console. Enter file for logging trace messages to a file, and Console to the command shell.

handler.custom_handler.details The path to the file where the trace messages should be logged in case of a file.

handler.custom_handler.isAbsolutePath Set this to true if the path given above is an absolute path, and false, if otherwise.

handler.custom_handler.appendIfFileExists This can be either true or false. If true, trace methods are appended at the end of the file, if it exists. If set to false, the trace file is overwritten.

handler.custom_handler.loglevel Loglevels can be specified here. The following log levels are available: event, debug, off, info, user, finer, severe, warning, and all.

handler.custom_handler.contexttype.packages All relevant trace methods that occur in a given package are logged in the trace file.

enable.debug Valid values are true or false. Set this to true if debug messages should appear while tracing.

Related Topics:

Property	Description

handlers	This is a place holder for the kind of handlers. There can be a number of handlers available doing various types of tracing. Here the entry custom_handler provides the reference to the current handler.
handler.custom_handler.type	Tracing can happen either to a file or to the Console. Enter file for logging trace messages to a file, and Console to the command shell.
handler.custom_handler.details	The path to the file where the trace messages should be logged in case of a file.
handler.custom_handler.isAbsolutePath	Set this to true if the path given above is an absolute path, and false, if otherwise.
handler.custom_handler.appendIfFileExists	This can be either true or false. If true, trace methods are appended at the end of the file, if it exists. If set to false, the trace file is overwritten.
handler.custom_handler.loglevel	Loglevels can be specified here. The following log levels are available: event, debug, off, info, user, finer, severe, warning, and all.
handler.custom_handler.contexttype.packages	All relevant trace methods that occur in a given package are logged in the trace file.
enable.debug	Valid values are true or false. Set this to true if debug messages should appear while tracing.


© Pramati Technologies 2007	Runs on Pramati Server \| Feedback \| Legal