Most likely, a non-daemon thread is running. JVM's do not shutdown until there are 0 non-daemon threads. You will need to perform a thread dump [kill -3 pid for Unix or CTRL+Break for Windows] to determine the code which started the thread.

Second part: You have to make Jakarta Commons Logging use the x4juli JCLFactory. There are two possibilities: Specify a system property on your jvm startup (script): -Dorg.apache.commons.logging.LogFactory=org.x4juli.JCLFactory or put in an commons-logging.properties file in your classpath with org.apache.commons.logging.LogFactory=org.x4juli.JCLFactory property line in the file.

By fail-stop, we mean that log4j will not throw unexpected exceptions at run-time potentially causing your application to crash. If for any reason, log4j throws an uncaught exception, please send an email to the log4j-user@logging.apache.org mailing list. Uncaught exceptions are handled as serious bugs requiring immediate attention. Moreover, log4j will not revert to System.out or System.err when its designated output stream is not opened, is not writable or becomes full.

Log4j is the way Openbravo saves logs (errors or information about the application data). Logs are very useful in order to know where and why the application crashed. Log4j configuration is managed with /tomcat/webapps/openbravo/WEB-INF/log4j.lcf file, here is defined where the log will be stored, this is done in a line that looks like: The previous line means that the log is stored in /tomcat/logs/log4j_TAD.log file.

Because log4j is configured by default to log to a file, you may want to remove it from the implementaton. Doing this is quite simple - modify gov.nist.core.LogWriter.java. You can change its behavior to log to a network connection or remove it entirely and convert to println. The Listener may have blocked while processing a transaction. Do not block in your listener method. If you need to block, start a thread and block in it dont block in the thread that you were called in the listener.

If you have to use commons-logging (for example the jar is required by certain bundles) then try using the most recent version commons-logging version (1.1+) as it provides more options on the discovery process. Below are some settings that can be used to make commons-logging work inside an OSGi environment: Unfortunately, commons-logging 1.0.x uses the thread context class loader (TCCL) always for loading loggers implementations.

The ogsilogging.properties file contains the log filter settings you would need to change. This file must be in your current directory or in the classpath in order to be correctly read by our container. When deploying your services into Tomcat this file ends up in webapps/ogsa/WEB-INF. In order to read the settings in this file after your modifications you need to add that directory to your CLASSPATH variable before you start tomcat.

Although both APIs are conceptually similar, the log4j API is significantly more flexible and offers many more features, too numerous to be listed here. You will discover that the additional features and flexibility turn out to be indispensable in the context of a mission-critical application. The open and collaborative way in which log4j is developped ensures that it continues to preserve and even widen its competitive edge.

We recommend to switch the default buffer type to 'heap' by inserting the following code before you start a server: If you prefer direct buffers to heap buffers, JVM might have ran out of direct memory. Please try increasing maximum direct memory size using -XX:MaxDirectMemorySize option (e.g. -XX:MaxDirectMemorySize=128M) Please make sure if you called ByteBuffer.flip() to flip the buffer before writing the buffer out. It is a common mistake NIO beginners make.

Embedded components such as libraries do not need and should not configure the logging system. They invoke SLF4J to log but should let the end-user configure the logging environment. When embedded components try to configure logging on their own, they often override the end-user's wishes. At the end of the day, it is the end-user who has to read the logs and process them. She should be the person to decide how she wants her logging configured.

This is an x4juli FAQ. Please have a look at the project pages for their documentation regarding usage in user code.

This description is based on Tomcat 5.5.12. First rename x4juli-x.x.jar to tomcat-juli.jar and put it in {tomcat_installation_directory}/bin (you have to overwrite the existing file).

Look at the Session manager component and tweak accordingly. One way is to tell tomcat to persist sessions to a path which does not exist. (So tomcat will not store, or be able to load the sessions)

In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4j it is possible to enable logging at runtime without modifying the application binary. The log4j package is designed so that log statements can remain in shipped code without incurring a high performance cost. It follows that the speed of logging (or rather not logging) is capital. the same time, log output can be so voluminous that it quickly becomes overwhelming.

The commons-logging project provides the commons-logging API (commons-logging-api-nn.jar) along with an implementation (commons-logging-adapters-nn.jar) that provides a wrapper between the API and the actual logging libraries used underneath (such as log4j, java.util.logging, etc). However, in order to determine what implementation should be used, commons-logging library tries to do some classloading-based discovery that is fragile and can fail unexpectedly.

Although both APIs are conceptually similar, the log4j API is significantly more flexible and offers many more features, too numerous to be listed here. You will discover that the additional features and flexibility turn out to be indispensable in the context of a mission-critical application. The open and collaborative way in which log4j is developped ensures that it continues to preserve and even widen its competitive edge.

x4juli provides a native implementation for org.apache.commons.logging.Log interface and for the org.slf4j.Logger interface. x4juli uses the standard way of each facade to implement the corresponding factory. In case of Jakarta Commons Logging you still have to use the originally provided jar and put an config entry in the right place (System property or config.file). In case of slf4j you have to do nothing but remove all other sl4fj-xxxxx.jar files from the classpath.

Long answer: Java Commons Logging introduces a classloader hell that is discussed to some extend by the author of Log4J here and here. Thus, Coverlipse adds the Java Commons Logging package to those handled by the system classloader. This way, projects that use Java Commons Logging can be tested with Coverlipse. However, it is not possible to test the Java Commons Logging itself with coverage by Coverlipse. Again, this is a problem occurring only with Eclipse 3.0.

Author: John Mitchell (http://www.jguru.com/guru/viewbio.jsp?EID=4) Question originally posed by Christopher Cavnor (http://www.jguru.com/guru/viewbio.jsp?EID=10464 If you're asking how to setup Tomcat to run servlets then you should probably start by reading the current version of the still nascent Tomcat User Guide. Comments and alternative answers Check the Developing Applications for Tomcat.html file in the tomcat\doc\devapp directory after download