View comments | RSS feed
JRun Administrator's Guide Previous Up One Level Next
Logging


Web service logging integration

The JRun web service engine, Apache Axis, uses Apache log4j as its logging system. JRun provides an integration layer that outputs Axis log messages to a JRun server's event log. Each log message is prefixed with the name of the Axis class that generated it.

The Axis log level matches the lowest JRun log level set to true in the jrun_root/servers/server_name/SERVER-INF/jrun.xml file. By default, INFO is the lowest log level set to true, so Axis log messages of priority INFO and higher are logged in the JRun event log.

The majority of Axis log messages are of priority DEBUG. Setting the DEBUG log level to true in the jrun.xml file lets you see exactly how Axis is handling each web service request and response. However, doing so adds a great deal of output to the log.

Log4j reads its configuration information from the log4j.properties file in the jrun_root/lib/jrun.jar file. To override the log4j.properties file, you can set the system property log4j.configuration to another properties file and configure log4j in any way appropriate for your configuration. Since JRun configuration is performed after configuration information is read from the properties file, it is still in effect when you provide your own log4j configuration.

Previous Up One Level Next

Comments


No screen name said on Oct 19, 2004 at 3:14 AM :
no log4j.properties in jrun.jar . I used jrun4.
jrunrandy said on Oct 19, 2004 at 7:10 AM :
This should say webservices.jar instead of jrun.jar.
vpd_ said on May 13, 2005 at 5:27 PM :
How can I set up this engine to switch to another logging, e.g. JDK 1.4 logging? Thanks
ErikYuzwa said on Aug 4, 2005 at 8:34 AM :
When providing your own Log4j jar and commons-logging.jar in your war file's WEB-INF/lib folder, you'll come across the problem of JRun not being able to find them.

The top-level properities file that this page of the documentation refers to will override your own app's log4j configuration.

The only way we found to get around this, was to include a jrun-web.xml file in your WAR file with the following tag:

<jrun-web-app>
<load-system-classes-first>false</load-system-classes-first>
</jrun-web-app>

 

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/logging6.htm