Re: Logging framework
Hi Mirunalini, Are you sure that the catalina.sh that you execute is actually picking up from the one that you have downloaded? Do you have any tomcat installed from other sources, such as from the centos 7.3? For a very long period of time, I have never seen Tomcat written as "jakarta-tomcat" in any of recent download versions (including version 7.0). It's been spun off from Apache Jakarta project long time ago. I suspect some of your configuration is actually picking up from the centos packaged version of tomcat. You can see whether there's a centos bundled tomcat installed by executing: sudo yum list | grep tomcat If it shows any tomcat, uninstall it using (I am assuming this is your development machine, not production machine): sudo yum remove Regards, Daniel Baktiar On Tue, Dec 12, 2017 at 5:43 PM, mirunalini Chandrasekaran < miru3...@gmail.com> wrote: > Hi, > > This is how i guess tomcat starts, and also it uses the startup script with > catalina.sh file. > > ps -ef | grep tomcat > > root 1357 1 0 11:53 ?00:00:08 > /usr/local/thirdparty/java/jdk/bin/java -classpath > :/usr/local/thirdparty/jakarta-tomcat/lib/javax.ws. > rs-api-2.0.jar:/usr/local/thirdparty/jakarta-tomca > /lib/jersey-client.jar:/usr/local/thirdparty/jakarta- > tomcat/lib/jersey-common.jar:/usr/local/thirdparty/jakarta- > tomcat/lib/hk2-api-2.3.0-b05.jar:/usr/local/thirdparty/ > jakarta-tomcat/lib/jersey-guava-2.10.1.jar:/usr/local/ > thirdparty/jakarta-tomcat/lib/javax-inject.jar:/usr/local/ > thirdparty/jakarta-tomcat/lib/hk2-locator-2.3.0-b05.jar:/ > usr/local/thirdparty/jakarta-tomcat/lib/hk2-utils-2.3.0- > b05.jar:/usr/local/thirdparty/jakarta-tomcat/lib/javax. > annotation-api-1.2.jar:/usr/local/thirdparty/jakarta- > tomcat/lib/catalina.jar:/usr/local/platform/jar/ > cucminventory-tcpserver.jar > com.cisco.cucminventory.server.MultiThreadedTCPServer > root 6115 5927 0 15:05 pts/000:00:00 grep --color=auto tomcat > root 27529 1 0 11:57 ?00:00:00 /home/tomcat/tomcat -user > tomcat -home /usr/local/thirdparty/java/j2sdk -pidfile > /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname > /home/tomcat/tomcat -outfile > /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile &1 > -Djava.library.path=/usr/local/cm/lib:/usr/local/lib:/ > usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/ > thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/ > usr/lib:/usr/local/cm/lib::/usr/local/platform/lib > -Djavax.net.ssl.trustStore=/usr/local/platform/.security/ > tomcat/trust-certs/tomcat-trust.keystore > -Djavax.net.ssl.trustStorePassword= > -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/ > logs/diagnostic-info.jvm-crash.%p.tomcat.txt > -Dsun.zip.disableMemoryMapping=true > -XX:OnOutOfMemoryError=/tomcat_diagnostics.sh > -XX:OnError=/tomcat_diagnostics.sh -Djdk.tls.ephemeralDHKeySize=2048 > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Dlog4j.configuration=file:/usr/local/thirdparty/jakarta- > tomcat/webapps/log4jinit/log4j.xml > -Xmx1824m -Xms256m -XX:MaxPermSize=448m > -Djava.endorsed.dirs=/usr/local/thirdparty/jakarta-tomcat/endorsed -cp > :/common/download:/usr/local/platform/application_locale/ > platform-api:/usr/local/platform/application_locale/cmplatform:/usr/local/ > platform/application_locale:/usr/local/cm/application_ > locale/cmservices:/usr/local/cm/application_locale/car:/ > usr/local/cm/application_locale/ccmadmin:/usr/local/cm/ > application_locale/ucmuser:/usr/local/cm/application_ > locale:/etc/opt/cisco/elm/server/resource:/usr/local/ > thirdparty/jakarta-tomcat/bin/bootstrap.jar::/usr/local/ > thirdparty/jakarta-tomcat/bin/tomcat-juli.jar > -Djava.security.policy==/usr/local/thirdparty/jakarta- > tomcat/conf/catalina.policy > -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat > -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat > -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp > org.apache.catalina.startup.Bootstrap start > tomcat 27530 27529 6 11:57 ?00:12:50 /home/tomcat/tomcat -user > tomcat -home /usr/local/thirdparty/java/j2sdk -pidfile > /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname > /home/tomcat/tomcat -outfile > /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile &1 > -Djava.library.path=/usr/local/cm/lib:/usr/local/lib:/ > usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/ > thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/ > usr/lib:/usr/local/cm/lib::/usr/local/platform/lib > -Djavax.net.ssl.trustStore=/usr/local/platform/.security/ > tomcat/trust-certs/tomcat-trust.keystore > -Djavax.net.ssl.trustStorePassword= > -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/ > logs/diagnostic-info.jvm-crash.%p.tomcat.txt > -Dsun.zip.disableMemoryMapping=true > -XX:OnOutOfMemoryError=/tomcat_diagnostics.sh > -XX:OnError=/tomcat_diagnostics.sh -Djdk.tls.ephemeralDHKeySize=2048 > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Re: Logging framework
Hi, This is how i guess tomcat starts, and also it uses the startup script with catalina.sh file. ps -ef | grep tomcat root 1357 1 0 11:53 ?00:00:08 /usr/local/thirdparty/java/jdk/bin/java -classpath :/usr/local/thirdparty/jakarta-tomcat/lib/javax.ws.rs-api-2.0.jar:/usr/local/thirdparty/jakarta-tomca /lib/jersey-client.jar:/usr/local/thirdparty/jakarta-tomcat/lib/jersey-common.jar:/usr/local/thirdparty/jakarta-tomcat/lib/hk2-api-2.3.0-b05.jar:/usr/local/thirdparty/jakarta-tomcat/lib/jersey-guava-2.10.1.jar:/usr/local/thirdparty/jakarta-tomcat/lib/javax-inject.jar:/usr/local/thirdparty/jakarta-tomcat/lib/hk2-locator-2.3.0-b05.jar:/usr/local/thirdparty/jakarta-tomcat/lib/hk2-utils-2.3.0-b05.jar:/usr/local/thirdparty/jakarta-tomcat/lib/javax.annotation-api-1.2.jar:/usr/local/thirdparty/jakarta-tomcat/lib/catalina.jar:/usr/local/platform/jar/cucminventory-tcpserver.jar com.cisco.cucminventory.server.MultiThreadedTCPServer root 6115 5927 0 15:05 pts/000:00:00 grep --color=auto tomcat root 27529 1 0 11:57 ?00:00:00 /home/tomcat/tomcat -user tomcat -home /usr/local/thirdparty/java/j2sdk -pidfile /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname /home/tomcat/tomcat -outfile /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile &1 -Djava.library.path=/usr/local/cm/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib::/usr/local/platform/lib -Djavax.net.ssl.trustStore=/usr/local/platform/.security/tomcat/trust-certs/tomcat-trust.keystore -Djavax.net.ssl.trustStorePassword= -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/logs/diagnostic-info.jvm-crash.%p.tomcat.txt -Dsun.zip.disableMemoryMapping=true -XX:OnOutOfMemoryError=/tomcat_diagnostics.sh -XX:OnError=/tomcat_diagnostics.sh -Djdk.tls.ephemeralDHKeySize=2048 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dlog4j.configuration=file:/usr/local/thirdparty/jakarta-tomcat/webapps/log4jinit/log4j.xml -Xmx1824m -Xms256m -XX:MaxPermSize=448m -Djava.endorsed.dirs=/usr/local/thirdparty/jakarta-tomcat/endorsed -cp :/common/download:/usr/local/platform/application_locale/platform-api:/usr/local/platform/application_locale/cmplatform:/usr/local/platform/application_locale:/usr/local/cm/application_locale/cmservices:/usr/local/cm/application_locale/car:/usr/local/cm/application_locale/ccmadmin:/usr/local/cm/application_locale/ucmuser:/usr/local/cm/application_locale:/etc/opt/cisco/elm/server/resource:/usr/local/thirdparty/jakarta-tomcat/bin/bootstrap.jar::/usr/local/thirdparty/jakarta-tomcat/bin/tomcat-juli.jar -Djava.security.policy==/usr/local/thirdparty/jakarta-tomcat/conf/catalina.policy -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp org.apache.catalina.startup.Bootstrap start tomcat 27530 27529 6 11:57 ?00:12:50 /home/tomcat/tomcat -user tomcat -home /usr/local/thirdparty/java/j2sdk -pidfile /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname /home/tomcat/tomcat -outfile /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile &1 -Djava.library.path=/usr/local/cm/lib:/usr/local/lib:/usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/usr/lib:/usr/local/cm/lib::/usr/local/platform/lib -Djavax.net.ssl.trustStore=/usr/local/platform/.security/tomcat/trust-certs/tomcat-trust.keystore -Djavax.net.ssl.trustStorePassword= -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/logs/diagnostic-info.jvm-crash.%p.tomcat.txt -Dsun.zip.disableMemoryMapping=true -XX:OnOutOfMemoryError=/tomcat_diagnostics.sh -XX:OnError=/tomcat_diagnostics.sh -Djdk.tls.ephemeralDHKeySize=2048 -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dlog4j.configuration=file:/usr/local/thirdparty/jakarta-tomcat/webapps/log4jinit/log4j.xml -Xmx1824m -Xms256m -XX:MaxPermSize=448m -Djava.endorsed.dirs=/usr/local/thirdparty/jakarta-tomcat/endorsed -cp :/common/download:/usr/local/platform/application_locale/platform-api:/usr/local/platform/application_locale/cmplatform:/usr/local/platform/application_locale:/usr/local/cm/application_locale/cmservices:/usr/local/cm/application_locale/car:/usr/local/cm/application_locale/ccmadmin:/usr/local/cm/application_locale/ucmuser:/usr/local/cm/application_locale:/etc/opt/cisco/elm/server/resource:/usr/local/thirdparty/jakarta-tomcat/bin/bootstrap.jar::/usr/local/thirdparty/jakarta-tomcat/bin/tomcat-juli.jar -Djava.security.policy==/usr/local/thirdparty/jakarta-tomcat/conf/catalina.policy -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp org.apache.catalina.startup.Bootstrap start Regards, Mirunalini On Fri, Dec 8, 2017 at 12:56 PM, Konstantin
Re: Logging framework
2017-12-08 9:58 GMT+03:00 mirunalini Chandrasekaran: > Hi All, > > I am using Tomcat 7.0.81 on centos 7.3 and using openjdk 1.7.0.141. Tomcat > was downloaded from http://tomcat.apache.org/ > > The problem I am seeing recently is manager*.log and localhost*.log files > are not created. Instead, I see the messages that were to be written into > manager.log are going into Catalina.out. catalina.out and > localhost_access.log continue to work like before. May I know how and from > where to start debugging this? > I have verified logging.properties, there is no issue with it. How do you start Tomcat? Overall, Tomcat uses the standard java.uti.logging API to perform its logging. The java.util.logging is configured via the following two system properties: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties These two properties are set by catalina.sh wrapper script when it launches java process for Tomcat If those properties are missing, the default configuration of java.util.logging is to log everything to a java.util.logging.ConsoleHandler. The stdout and stderr of the java process are redirected to "catalina.out" file by catalina.sh script. It is not a proper log file. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Logging framework
Hi All, I am using Tomcat 7.0.81 on centos 7.3 and using openjdk 1.7.0.141. Tomcat was downloaded from http://tomcat.apache.org/ The problem I am seeing recently is manager*.log and localhost*.log files are not created. Instead, I see the messages that were to be written into manager.log are going into Catalina.out. catalina.out and localhost_access.log continue to work like before. May I know how and from where to start debugging this? I have verified logging.properties, there is no issue with it. Regards, Mirunalini
Re: Logging framework !
2017-11-01 8:17 GMT+03:00 Utkarsh Dave: > Hi All, > > I am using Tomcat 7.0.81 on centos 7.2 and using openjdk 1.7.0.141. > The problem I am seeing recently is manager*.log and localhost*.log files > are not created. Instead, I see the messages that were to be written into, > manager.log are going into Catalina.out. catalina.out and > localhost_access.log continue to work like before. > May I know how and from where to start debugging this? > I have verified logging.properties, there is no issue with it. > My guess is that "java.util.logging.manager" and "java.util.logging.config.file" system properties are not set, and thus java uses default implementation of java.util.logging instead of the one provided by Tomcat's org.apache.juli.ClassLoaderLogManager. Those properties are usually set by catalina.sh (and there is a comment at that top of that file). Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Logging framework !
On 01.11.2017 06:17, Utkarsh Dave wrote: Hi All, I am using Tomcat 7.0.81 on centos 7.2 and using openjdk 1.7.0.141. The problem I am seeing recently is manager*.log and localhost*.log files are not created. Instead, I see the messages that were to be written into, manager.log are going into Catalina.out. catalina.out and localhost_access.log continue to work like before. May I know how and from where to start debugging this? I have verified logging.properties, there is no issue with it. Any help will be appreciable. The first question here is : where does that tomcat 7.0.81 come from ? If it is the "vanilla" tomcat from the tomcat website, then chances are that we can help you. If it is from a centos packaged version of tomcat, then there are less chances that we can help you, because we do not know exactly how the packagers of centos have set this up. You probably need to start in that case by looking at the startup script(s) of tomcat, in /etc/init.d or similar, to find out what happens in terms of redirection of logfiles etc. The people who create the tomcat packaged versions for the different Linux/Unix/Windows etc. distributions, each have their own logic about this kind of thing. Their intent is usually to try to "force" the tomcat logging to happen according to the general conventions on their particular platform, which can be quite different from the standard logging conventions of the various pieces of software that should run on each platform. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Logging framework !
Hi All, I am using Tomcat 7.0.81 on centos 7.2 and using openjdk 1.7.0.141. The problem I am seeing recently is manager*.log and localhost*.log files are not created. Instead, I see the messages that were to be written into, manager.log are going into Catalina.out. catalina.out and localhost_access.log continue to work like before. May I know how and from where to start debugging this? I have verified logging.properties, there is no issue with it. Any help will be appreciable. -Thanks Dave
Re: Logging framework for Tomcat -Exceptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kiran, On 7/11/12 11:33 PM, Kiran Badi wrote: I know this is not a place to learn Java and thats not my intention.Its time for me to implement robust logging framework,so thought let me ask here as which is light weight and yet can log exceptions preferably both handled and unhandled. No logging framework is going to catch your exceptions for you and magically log them: you'll have to catch them yourself and explicitly log them. You can easily write a Filter that you can plug-into any servlet container (including Tomcat) that will catch any exception you want a and log it any way you want. As for logging frameworks, I don't know of a single one that would somehow be incompatible with Tomcat. Good logging frameworks include: - - Apache log4j - - java.util.logging - - logback Or, you might prefer a meta logging package that can work with any of those: - - Apache commons-logging - - slf4j - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAAIyIACgkQ9CaO5/Lv0PDvpwCgtBCqisSe9kNB0v8Y8mAQPsiU 5rYAnjmZS9Ktn3ZrptUgFto7I2nD+Jz1 =QBHn -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Logging framework for Tomcat -Exceptions
Hi, I have below code for catching DAO exceptions,but I feel its not correct way to do this,Can some one point me to some library which will capture all exceptions which my code will throw and works with tomcat. I implementing Model2 mvc pattern and to my surprise I am able to show values to the view but database is not getting inserted.I am lost given that no exception is also being thrown anywhere.All logs looks clean but DB is not updated. import java.sql.Connection; public interface DAO { Connection getConnection() throws DAOException; } public class DAOException extends Exception { private static final long serialVersionUID = 19192L; public DAOException() { } public DAOException(String message) { this.message = message; } @Override public String getMessage() { return message; } public void setMessage(String message) { this.message = message; } private String message; @Override public String toString() { return message; } } - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Logging framework for Tomcat -Exceptions
On Thu, 2012-07-12 at 06:35 +0530, Kiran Badi wrote: Hi, I have below code for catching DAO exceptions, No, it's not. It's code that defines an interface and a poorly implemented exception type. There's no catching. Anywhere. but I feel its not correct way to do this,Can some one point me to some library which will capture all exceptions which my code will throw and works with tomcat. I implementing Model2 mvc pattern and to my surprise I am able to show values to the view but database is not getting inserted.I am lost given that no exception is also being thrown anywhere.All logs looks clean but DB is not updated. import java.sql.Connection; public interface DAO { Connection getConnection() throws DAOException; } public class DAOException extends Exception { private static final long serialVersionUID = 19192L; public DAOException() { } public DAOException(String message) { this.message = message; } @Override public String getMessage() { return message; } public void setMessage(String message) { this.message = message; } private String message; @Override public String toString() { return message; } } Other than including Tomcat in the subject, this has nothing to do with Tomcat. No offense, but this really isn't a list for teaching Java. But what the hell, I'll make one exception: public class DAOException extends Exception { public DAOException(String msg) { super(); } public DAOException(String msg) { super(msg); } public DAOException(String msg, Throwable cause) { super(msg, cause); } public DAOException(Throwable cause) { super(cause); } } That's all I'll say on this thread. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org signature.asc Description: This is a digitally signed message part
Re: Logging framework for Tomcat -Exceptions
On 7/12/2012 7:20 AM, Tim Watts wrote: No offense, but this really isn't a list for teaching Java. But what the hell, I'll make one exception: public class DAOException extends Exception { public DAOException(String msg) { super(); } public DAOException(String msg) { super(msg); } public DAOException(String msg, Throwable cause) { super(msg, cause); } public DAOException(Throwable cause) { super(cause); } } That's all I'll s say on this thread. I know Tim something was missing.Just 20 mins back I fixed the class,now I get the cool stack trace,damm it file upload stuff is breaking and passing null values.I will fix it. I know this is not a place to learn Java and thats not my intention.Its time for me to implement robust logging framework,so thought let me ask here as which is light weight and yet can log exceptions preferably both handled and unhandled. and thanks for some headsup. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Logging Framework
Meybe this one will help you: http://jamonapi.sourceforge.net/ Marcin Andrew Hole wrote: Hello! My java application writes relevant log of database procedures executions. My goal is to develop a report at intervals of 30 minutes with a summary, including requests slowest, and average time of execution, etc. 2007-11-26 00:00:00379 DEBUG ajp - 8009-10 RequestFilter - Request Started 2007-11-26 00:00:00379 DEBUG ajp - 8009-14 RequestFilter - Request Started 2007-11-26 00:00:00379 DEBUG ajp - 8009-10 RequestFilter - Request Ended: Total time: 0 s 2007-11-26 00:00:00379 DEBUG ajp - 8009-14 RequestFilter - Request Ended: Total time: 0 s Is there any framework adaptable to this? Best Regards - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Logging Framework
gee! moskito.anotheria.net exact this ready to use. On Nov 26, 2007 1:27 PM, Andrew Hole [EMAIL PROTECTED] wrote: Hello! My java application writes relevant log of database procedures executions. My goal is to develop a report at intervals of 30 minutes with a summary, including requests slowest, and average time of execution, etc. 2007-11-26 00:00:00379 DEBUG ajp - 8009-10 RequestFilter - Request Started 2007-11-26 00:00:00379 DEBUG ajp - 8009-14 RequestFilter - Request Started 2007-11-26 00:00:00379 DEBUG ajp - 8009-10 RequestFilter - Request Ended: Total time: 0 s 2007-11-26 00:00:00379 DEBUG ajp - 8009-14 RequestFilter - Request Ended: Total time: 0 s Is there any framework adaptable to this? Best Regards - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Logging Framework
Hello! My java application writes relevant log of database procedures executions. My goal is to develop a report at intervals of 30 minutes with a summary, including requests slowest, and average time of execution, etc. 2007-11-26 00:00:00379 DEBUG ajp - 8009-10 RequestFilter - Request Started 2007-11-26 00:00:00379 DEBUG ajp - 8009-14 RequestFilter - Request Started 2007-11-26 00:00:00379 DEBUG ajp - 8009-10 RequestFilter - Request Ended: Total time: 0 s 2007-11-26 00:00:00379 DEBUG ajp - 8009-14 RequestFilter - Request Ended: Total time: 0 s Is there any framework adaptable to this? Best Regards - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]