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.

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. See similar questions...

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. See similar questions...

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. See similar questions...

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. See similar questions...

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

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). See similar questions...

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. See similar questions...

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. See similar questions...

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. See similar questions...

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 See similar questions...

Author: Will Stranathan (http://www.jguru.com/guru/viewbio.jsp?EID=98224) Question originally posed by Kevin Kovach (http://www.jguru.com/guru/viewbio.jsp?EID=35628 http://java.apache.org/jservssi/ - the JServ JSSI servlet should do the trick. Comments and alternative answers From the tomcat-user mailing list: From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com> To: tomcat-user@jakarta.apache. See similar questions...

Author: Roger Sergeant (http://www.jguru.com/guru/viewbio.jsp?EID=125277) Question originally posed by archana sahu (http://www.jguru.com/guru/viewbio.jsp?EID=112286 Why would you want to do this? Is there a reason for you needing to run 2 servlet-enabled webservers together. Well, one reason might be that Tomcat may support a more recent version of the spec, or that iPlanet may have bugs that Tomcat does not... But at the moment, they both allegedly support version 2.2 of the Servlet spec. See similar questions...

Author: Brian Ewins (http://www.jguru.com/guru/viewbio.jsp?EID=301660) Question originally posed by Guy Zürcher (http://www.jguru.com/guru/viewbio.jsp?EID=203476 This is described in the Tomcat User Guide at: http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/uguide/tomcat_ug.html Look for the section called "Making Apache Serve your Context's Static Files" Comments and alternative answers See similar questions...

First create a certificate keystore for tomcat by executing $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA Restart httpd, tomcat and opennms just to be sure and after what seemed too long, I was prompted for user name and password. It seems only the first time connecting is real slow, subsequent logins are quite speedy. I wanted to add a few comments to this. First, if you want to use a password other than "changeit", add the keystorePass attribute: <Connector className="org.apache. See similar questions...

You configure each section (numbered 1-10) by pointing DSpy to the proper directory on your network. By putting a shortcut to DSpy in your startup folder, it will start with your TSC client during every boot/login and automatically start tracking your TSC progress. See similar questions...

quot;Tomcat is a free, open-source implementation of Java Servlet and JavaServer Pages technologies developed under the Jakarta project at the Apache Software Foundation. Tomcat is available for commercial use under the ASF license from the Apache web site in both binary and source versions." They have client software available for a number of operating systems. See similar questions...

Download and install the apt for your current fedora core version, and add the repositories for fedora core 5 to the /etc/apt/sources.list, to do simply replace the old one with this new sources.list, remove the files form /etc/apt/sources.list.d directory, then do: to refresh cache and get new online packages you need to run the apt-get update, frequently, read man apt-get for help. See similar questions...

Yum is included in the fedora core installation, to use yum one should add the fedora core release, freshrpms, newrpms, dag, dries, livna and atrpms to the directory /etc/yum.repos.d. you can add the following repos, just download and install the rpm files, these will add the related repos to the /etc/yum.repos.d: Fedora core release repos is installed by defualt one don't need to install them: fedora-release-5-5.noarch. See similar questions...