|
Problem(Abstract) |
Debug custom advisors using the ADVLOG and the
System.out.println command. |
|
|
|
Cause |
When creating custom advisors, it is helpful to use the
ADVLOG (level set to message) to verify that the advisor works as
expected. This writes messages to the advisor's logfile when the log level
is less than the level associated with the advisor. A logging level of 0
indicates that messages are always written to the logfile. However, you
cannot use the ADVLOG from the constructor. The logfile is not created
until after the custom advisor's constructor is completed. |
|
|
Resolving the
problem |
To avoid this limitation and to debug your custom advisor,
use the System.out.println (message) command to write messages to a
window. Edit the ndserver script and change javaw to java™
for the messages to appear. If you are using the Microsoft® Windows® 2000
operating system, stop the Dispatcher from running as a service, then
manually start it from a window to see the messages. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Edge Server |
Load Balancer |
AIX, Linux, Solaris, Windows 2000, Windows NT |
Edge Server 2.0 GA, Edge Server 2.0 NLV, Edge Server 2.0 PTF1, Edge
Server 2.0 PTF2 |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|