User Guide
|
 |
 |
|
 |
 |
Debugging AquaLogic Service Bus
This section provides information about enabling debugging for different modules in AquaLogic Service Bus. You can enable and disable debugging by modifying the corresponding entries in the wlidebug.xml file, which is located in the root directory of the AquaLogic Service Bus domain. If the wlidebug.xml file is not in the root directory or if it has been deleted, it is created again without any contents when the server starts. The following listing provides an example of the contents of the wlidebug.xml file with debugging disabled for all modules (all entries set to false).
<?xml version='1.0' encoding='UTF-8'?>
<java:wli-debug-logger xmlns:java="java:com.bea.wli.debug">
<n1:Name xmlns:n1="java:weblogic.diagnostics.debug">wlidebug</n1:Name>
<java:wli-management-debug>false</java:wli-management-debug>
<java:wli-monitoring-debug>false</java:wli-monitoring-debug>
<java:wli-management-dashboard-debug>false</java:wli-management-dashboard-debug>
<java:wli-config-debug>false</java:wli-config-debug>
<java:wli-config-transaction-debug>false</java:wli-config-transaction-debug>
<java:wli-config-deployment-debug>false</java:wli-config-deployment-debug>
<java:wli-config-component-debug>false</java:wli-config-component-debug>
<java:wli-sb-transports-debug>false</java:wli-sb-transports-debug>
<java:wli-sb-pipeline-debug>false</java:wli-sb-pipeline-debug>
<java:wli-alert-manager-debug>false</java:wli-alert-manager-debug>
<java:wli-jms-reporting-provider-debug>false</java:wli-jms-reporting-provider-debug>
<java:wli-monitoring-aggregator-debug>false</java:wli-monitoring-aggregator-debug>
< java:wli-credential-debug >false</java:wli-credential-debug >
< java:wli-management-common-debug >false</java:wli-management-common-debug >
</java:wli-debug-logger>
Although debugging should be disabled during normal AquaLogic Service Bus operation, you may find it helpful to turn on certain debug flags while you are developing your solution and experimenting with it for the first time. For example, you may want to turn on the alert debugging flag when you are developing alerts and would like to investigate how the alert engine works.
Some of the available debug flags are:
wli-config-debug—Provides information on general aspects of AquaLogic Service Bus configuration.wli-config-deployment-debug— Provides debug information on session creation, activation, and distribution of configuration in a cluster.wli-config-transaction-debug—Provides low level debug information about changes made to in-memory data structures and files. This alert flag also generates server startup recovery logs.wli-config-component-debug—Provides low level debug information about create, update, delete, and import operations.wli-sb-transports-debug—Provides transport related debug information, including transport headers, which is printed per-message.wli-sb-pipeline-debug—Prints errors that are generated within the pipeline.wli-alert-manager-debug—Prints an evaluation of alerts.
All other debug flags are self explanatory.
For all flags, debug information is logged to the server log at {domaindir}/servers/{servername}/logs/{servername}.log, except for the wli-monitoring-aggregator-debug flag. The wli-monitoring-aggregator-debug flag enables debugging for aggregator. This flag logs the aggregated document every minute and stores the log files in the {domain}\monitoring folder.
Note: Turning the wli-monitoring-aggregator-debug flag on generates large amounts of debug data. Therefore, you should only use this flag for debugging purposes for short periods of time.
