RE: Reloadable context
Hi , just wondering if anyone has come across similar problem (pls refer to the email below). Kind regards, Alex. -Original Message- From: Akoulov, Alexandre [SB] Sent: Wednesday, 17 May 2006 2:17 PM To: Tomcat Users List Subject: Reloadable context Hi , I am using tomcat-5.5.12 and would like it to auto reload my web app as soon as it detects the change of the web app class(es). That's why i've turned on the reloadable attribute of the Context element that defines my web app: Context path=/myWebApp docBase=/home/testUser/myWebApp reloadable=true crossContext=true allowLinking=true / It does not seem to work. When I recompile one of myWebApp's servlets tomcat detects the change but then throws a warning: May 17, 2006 7:33:41 AM org.apache.catalina.core.StandardContext reload INFO: Reloading this Context has started May 17, 2006 7:34:01 AM org.apache.catalina.core.ApplicationDispatcher invoke WARNING: Servlet invoker is currently unavailable So I've got to restart tomcat to get my change deployed. Any idea on what I am missing? Thanks a lot. Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: is it ok to run tomcat 3.3 in jre 1.4?
thanks a lot, Doug. I am interested to know if there is anyone who runs tomcat 3.3 in java 1.4. As far as I remember when tomcat 3.3 was released we were still in java 1.3 world and therefore I assume no proper testing was done on tomcat 3.3 in java 1.4 environment. Kind regards, Sasha. -Original Message- From: Parsons Technical Services [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 February 2006 7:00 PM To: Tomcat Users List Subject: Re: is it ok to run tomcat 3.3 in jre 1.4? Yes. By the nature of the design, Java is almost always backward compatible in that older software will run on newer versions. As usual there are sometimes exceptions to this. If you are going to change Java version, you may wish to change it to the current version. 1.5 is very stable, compatible and reported to be much faster. Again there are never any guarantees. Only by doing it will you know for sure. Doug - Original Message - From: Akoulov, Alexandre [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, February 15, 2006 11:08 PM Subject: is it ok to run tomcat 3.3 in jre 1.4? Hi all, we need to urgently fix one web app that runs in tc 3/ java 1.3. The fix is only available with java 1.4. My question is: can we run tomcat 3.3 in java 1.4.2_10 Kind regards, Sasha. -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 February 2006 2:58 PM To: Tomcat Users List Subject: RE: New to apache / Tomcat From: Andrew English [mailto:[EMAIL PROTECTED] Subject: RE: New to apache / Tomcat Could it be they are running both? Certainly could be, but I would have to wonder why... I looked through all the jboss folders and found nothing related to catalina just the files which make up the web site itself. I suppose it could be just left-over naming from some ambitious full J2EE project that ended up needing only Servlet/JSP capabilities. What are the dates on some of the files? Tomcat 4.0.3 came out in the spring of 2002, whereas JBoss 4.0.3 is fairly recent (mid-year 2005, SP1 in the fall). You might try downloading whichever one corresponds to the dates you find, and comparing the directory structure of that with what you've got in hand. The Tomcat 4.0.3 archive is here: http://archive.apache.org/dist/tomcat/tomcat-4/archive/v4.0.3/ - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
is it ok to run tomcat 3.3 in jre 1.4?
Hi all, we need to urgently fix one web app that runs in tc 3/ java 1.3. The fix is only available with java 1.4. My question is: can we run tomcat 3.3 in java 1.4.2_10 Kind regards, Sasha. -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Thursday, 16 February 2006 2:58 PM To: Tomcat Users List Subject: RE: New to apache / Tomcat From: Andrew English [mailto:[EMAIL PROTECTED] Subject: RE: New to apache / Tomcat Could it be they are running both? Certainly could be, but I would have to wonder why... I looked through all the jboss folders and found nothing related to catalina just the files which make up the web site itself. I suppose it could be just left-over naming from some ambitious full J2EE project that ended up needing only Servlet/JSP capabilities. What are the dates on some of the files? Tomcat 4.0.3 came out in the spring of 2002, whereas JBoss 4.0.3 is fairly recent (mid-year 2005, SP1 in the fall). You might try downloading whichever one corresponds to the dates you find, and comparing the directory structure of that with what you've got in hand. The Tomcat 4.0.3 archive is here: http://archive.apache.org/dist/tomcat/tomcat-4/archive/v4.0.3/ - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Encrypting ajp13 traffic
Yes, i've got similar setup . We might end up setting up ssh tunnelling as well. Kind regards, Sasha. -Original Message- From: David Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, 14 February 2006 8:18 AM To: Tomcat Users List Subject: Re: Encrypting ajp13 traffic While I can't speak for the O.P., I have had need for this myself once upon a time. Consider a setup where the content has to be secured via SSL and communication to/from the tomcat is over untrusted infrastructure SSL can't be proxied, so there is a need for the AJP/13 communication to be encrypted. My solution at the time was to setup a SSH tunnel between the two systems. It would be nice to have some form of encryption optionally available. Food for thought. -- David Mark Thomas wrote: Akoulov, Alexandre wrote: I am wondering if there is a way encrypt the traffic between apache and tomcat when they talk to each other on ajp13. Why do you want to do this? What requirement are you trying to meet / security threat are you trying to mitigate? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Smith Network Operations Supervisor Department of Entomology Cornell University 2132 Comstock Hall Ithaca, NY 14853 Phone: (607) 255-9571 Fax: (607) 255-0940 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Encrypting ajp13 traffic
Hi all, I am wondering if there is a way encrypt the traffic between apache and tomcat when they talk to each other on ajp13. All suggestions are welcome. Kind regards, Sasha. -Original Message- From: Ian Buzer [mailto:[EMAIL PROTECTED] Sent: Saturday, 11 February 2006 2:44 AM To: 'Tomcat Users List' Subject: RE: Tomcat - blank page problem Webpages seem to be loading then usually blank page comes(totaly blank no error messages) on high traffic. I suspect this could either be your redirector cachesize is not large enough (the number of threads that the redirector will accept from IIS) or tomcat is not able to respond to all the threads that are being passed through to it. Both these will show up in the isapi redirector logs. Cache size is set in /conf/workers.properties Tomcat threads are set in /conf/server.xml (maxThreads etc. on the AJP connector) Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.5.x and java 1.4.x
Hi all, Some time ago I built Tomcat 5.5.12 from source with java 1.5.0_05 and then ran it with the same java version (ie 1.5.0_05). However, our requirements have changed since then and now I need to run Tomcat 5.5.12 in java 1.4.2_10. I've dropped the content of the 'compat' directory into the Tomcat5.5.12 installation directory (as per instructions found on http://tomcat.apache.org/tomcat-5.5-doc/building.html and also in RUNNING.txt). Then tried to start tomcat and got java.lang.UnsupportedClassVersionError, which in our case indicates that classes that were compiled with the lower java version attempt to run in the higher java version. This is exactly what I expected. However, when doing the same thing with the Tomcat 5.5.12 binaries downloaded directly from the tomcat.apache.org I was surprised to find that it started successfully. My question is: was Tomcat 5.5.12 binary version that can be downloaded from http://tomcat.apache.org/download-55.cgi#5.5.12 compiled with java 1.4? Thanks a lot for your help on this issue. Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.5.x and java 1.4.x
now I am trying to compile Tomcat5.5.12 with java 1.4.2_10 and getting the following error: build-catalina-core: [javac] Compiling 318 source files to /home/aa05584/tmp/apache-tomcat-5.5.12-src_hasBuildWithJava1.4.2_10/jakarta-tomcat-5/build/classes [javac] /home/aa05584/tmp/apache-tomcat-5.5.12-src_hasBuildWithJava1.4.2_10/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/Container.java:23: cannot access javax.servlet.ServletException [javac] bad class file: /software/local/java/packages/servletapi/servletapi-2.4/lib/servlet-api.jar(javax/servlet/ServletException.class) [javac] class file has wrong version 49.0, should be 48.0 [javac] Please remove or make sure it appears in the correct subdirectory of the classpath. [javac] import javax.servlet.ServletException; [javac] ^ [javac] 1 error Any ideas on what's going on? Kind regards, Sasha. -Original Message- From: Akoulov, Alexandre [IT] Sent: Monday, 9 January 2006 3:28 PM To: Tomcat Users List Subject: Tomcat 5.5.x and java 1.4.x Hi all, Some time ago I built Tomcat 5.5.12 from source with java 1.5.0_05 and then ran it with the same java version (ie 1.5.0_05). However, our requirements have changed since then and now I need to run Tomcat 5.5.12 in java 1.4.2_10. I've dropped the content of the 'compat' directory into the Tomcat5.5.12 installation directory (as per instructions found on http://tomcat.apache.org/tomcat-5.5-doc/building.html and also in RUNNING.txt). Then tried to start tomcat and got java.lang.UnsupportedClassVersionError, which in our case indicates that classes that were compiled with the lower java version attempt to run in the higher java version. This is exactly what I expected. However, when doing the same thing with the Tomcat 5.5.12 binaries downloaded directly from the tomcat.apache.org I was surprised to find that it started successfully. My question is: was Tomcat 5.5.12 binary version that can be downloaded from http://tomcat.apache.org/download-55.cgi#5.5.12 compiled with java 1.4? Thanks a lot for your help on this issue. Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TryNo2: path attribute for Context element in tomcat 5.5
thanks a lot, Hassan and Chuck, for your replies. Context element description (http://tomcat.apache.org/tomcat-5.5-doc/config/context.html) : path... The context path of this web application...The value of this field must not be set except when statically defining a Context in server.xml, as it will be infered from the filenames used for either the .xml context file or the docBase. I just find it a bit strange that tomcat5 derives the Context path from the actual filename. Was not the tomcat3 way of setting the context path in the 'path' attribute better? Does anyone know the story behind this change? Kind regards, Alex. -Original Message- From: Hassan Schroeder [mailto:[EMAIL PROTECTED] Sent: Friday, 25 November 2005 2:47 AM To: Tomcat Users List Subject: Re: TryNo2: path attribute for Context element in tomcat 5.5 Akoulov, Alexandre [IT] wrote: I am just wondering if you have any comments on the following email: Is it a right way to configure a context ? You configured it one way and it didn't work. You configured it *per the documentation* and it *did* work. What kind of comment would seem to be necessary? :-) -- Hassan Schroeder - [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: path attribute for Context element in tomcat 5.5
I'd greatly appreciate if you could give me the feedback on the following email: -Original Message- From: Akoulov, Alexandre [IT] Sent: Wednesday, 23 November 2005 12:16 PM To: Tomcat Users List Subject: path attribute for Context element in tomcat 5.5 Hi all, I am in the process of upgrading from tomcat-3.3 to tomcat-5.5.12. One of the changes in tomcat 5.5 is the configuration of contexts (ie web apps) is now being done in individual files (with a .xml extension) in the $CATALINA_HOME/conf/[enginename]/[hostname]/ directory ( rather than in $CATALINA_HOME/conf/server.xml, which is a tomcat-3.3 way). To test this new configuration I've created the $CATALINA_HOME/conf/Catalina/localhost/test.xml with the following content: - ?xml version='1.0' encoding='utf-8'? Contextpath=/testProjYY docBase=/home/alex/release/TestProj/war reloadable=true crossContext=true allowLinking=true Logger className=org.apache.catalina.logger.FileLogger directory=/home/alex/release/tomcat-5.5/logs prefix=localhost_log_TestProj. suffix=.txt timestamp=true/ /Context - As you can see the 'path' attribute is '/testProjYY' and in order to access this app I tried to hit http://sydap42d.aus.nsroot.net:8080/testProjYY/TestServlet url and I got 404 (The requested resource (/testProjYY/TestServlet) is not available.) error. So I went to Context element description (http://tomcat.apache.org/tomcat-5.5-doc/config/context.html) and found the following : path... The context path of this web application...The value of this field must not be set except when statically defining a Context in server.xml, as it will be infered from the filenames used for either the .xml context file or the docBase. Last sentence indicates that the 'path' attribute value is ignored, unless Context element is defined in server.xml (which is not encouraged in tomcat-5.5), and .xml file name is used as a context path instead. Therefore I've modified $CATALINA_HOME/conf/Catalina/localhost/test.xml (got rid of the 'path' tag): - Context docBase=/home/alex/release/TestProj/war reloadable=true crossContext=true allowLinking=true Logger className=org.apache.catalina.logger.FileLogger directory=/home/alex/release/tomcat-5.5/logs prefix=localhost_log_TestProj. suffix=.txt timestamp=true/ /Context - Then I hit http://sydap42d.aus.nsroot.net:8080/test/TestServlet (/test context path is derived from $CATALINA_HOME/conf/Catalina/localhost/test.xml filename) and got the html generated by TestServlet. Is it a right way to configure a context ? It just seems a bit strange that the 'path' attribute is completely ignored and instead the filename is used as a context path. Thanks a lot for your time and assistance on this matter. Kind regards, Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: path attribute for Context element in tomcat 5.5
woops, sent it by mistake, just ignore please :) -Original Message- From: Akoulov, Alexandre [IT] Sent: Thursday, 24 November 2005 5:51 PM To: Tomcat Users List Subject: RE: path attribute for Context element in tomcat 5.5 I'd greatly appreciate if you could give me the feedback on the following email: -Original Message- From: Akoulov, Alexandre [IT] Sent: Wednesday, 23 November 2005 12:16 PM To: Tomcat Users List Subject: path attribute for Context element in tomcat 5.5 Hi all, I am in the process of upgrading from tomcat-3.3 to tomcat-5.5.12. One of the changes in tomcat 5.5 is the configuration of contexts (ie web apps) is now being done in individual files (with a .xml extension) in the $CATALINA_HOME/conf/[enginename]/[hostname]/ directory ( rather than in $CATALINA_HOME/conf/server.xml, which is a tomcat-3.3 way). To test this new configuration I've created the $CATALINA_HOME/conf/Catalina/localhost/test.xml with the following content: - ?xml version='1.0' encoding='utf-8'? Contextpath=/testProjYY docBase=/home/alex/release/TestProj/war reloadable=true crossContext=true allowLinking=true Logger className=org.apache.catalina.logger.FileLogger directory=/home/alex/release/tomcat-5.5/logs prefix=localhost_log_TestProj. suffix=.txt timestamp=true/ /Context - As you can see the 'path' attribute is '/testProjYY' and in order to access this app I tried to hit http://sydap42d.aus.nsroot.net:8080/testProjYY/TestServlet url and I got 404 (The requested resource (/testProjYY/TestServlet) is not available.) error. So I went to Context element description (http://tomcat.apache.org/tomcat-5.5-doc/config/context.html) and found the following : path... The context path of this web application...The value of this field must not be set except when statically defining a Context in server.xml, as it will be infered from the filenames used for either the .xml context file or the docBase. Last sentence indicates that the 'path' attribute value is ignored, unless Context element is defined in server.xml (which is not encouraged in tomcat-5.5), and .xml file name is used as a context path instead. Therefore I've modified $CATALINA_HOME/conf/Catalina/localhost/test.xml (got rid of the 'path' tag): - Context docBase=/home/alex/release/TestProj/war reloadable=true crossContext=true allowLinking=true Logger className=org.apache.catalina.logger.FileLogger directory=/home/alex/release/tomcat-5.5/logs prefix=localhost_log_TestProj. suffix=.txt timestamp=true/ /Context - Then I hit http://sydap42d.aus.nsroot.net:8080/test/TestServlet (/test context path is derived from $CATALINA_HOME/conf/Catalina/localhost/test.xml filename) and got the html generated by TestServlet. Is it a right way to configure a context ? It just seems a bit strange that the 'path' attribute is completely ignored and instead the filename is used as a context path. Thanks a lot for your time and assistance on this matter. Kind regards, Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
path attribute for Context element in tomcat 5.5
Hi all, I am in the process of upgrading from tomcat-3.3 to tomcat-5.5.12. One of the changes in tomcat 5.5 is the configuration of contexts (ie web apps) is now being done in individual files (with a .xml extension) in the $CATALINA_HOME/conf/[enginename]/[hostname]/ directory ( rather than in $CATALINA_HOME/conf/server.xml, which is a tomcat-3.3 way). To test this new configuration I've created the $CATALINA_HOME/conf/Catalina/localhost/test.xml with the following content: - ?xml version='1.0' encoding='utf-8'? Contextpath=/testProjYY docBase=/home/alex/release/TestProj/war reloadable=true crossContext=true allowLinking=true Logger className=org.apache.catalina.logger.FileLogger directory=/home/alex/release/tomcat-5.5/logs prefix=localhost_log_TestProj. suffix=.txt timestamp=true/ /Context - As you can see the 'path' attribute is '/testProjYY' and in order to access this app I tried to hit http://sydap42d.aus.nsroot.net:8080/testProjYY/TestServlet url and I got 404 (The requested resource (/testProjYY/TestServlet) is not available.) error. So I went to Context element description (http://tomcat.apache.org/tomcat-5.5-doc/config/context.html) and found the following : path... The context path of this web application...The value of this field must not be set except when statically defining a Context in server.xml, as it will be infered from the filenames used for either the .xml context file or the docBase. Last sentence indicates that the 'path' attribute value is ignored, unless Context element is defined in server.xml (which is not encouraged in tomcat-5.5), and .xml file name is used as a context path instead. Therefore I've modified $CATALINA_HOME/conf/Catalina/localhost/test.xml (got rid of the 'path' tag): - Context docBase=/home/alex/release/TestProj/war reloadable=true crossContext=true allowLinking=true Logger className=org.apache.catalina.logger.FileLogger directory=/home/alex/release/tomcat-5.5/logs prefix=localhost_log_TestProj. suffix=.txt timestamp=true/ /Context - Then I hit http://sydap42d.aus.nsroot.net:8080/test/TestServlet (/test context path is derived from $CATALINA_HOME/conf/Catalina/localhost/test.xml filename) and got the html generated by TestServlet. Is it a right way to configure a context ? It just seems a bit strange that the 'path' attribute is completely ignored and instead the filename is used as a context path. Thanks a lot for your time and assistance on this matter. Kind regards, Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
default logging in tomcat 5.5
Hi all,
I am in the process of upgrading from tomcat-3.3 to tomcat-5.5 and would
greatly appreciate if you could let me know whether I understood tomcat-5.5's
default logging correctly.
As of tomcat 5.5 Context element does not have a Logger sub-element. Logging
can be configured with log4j or java.util.logging. I went with
java.util.logging, which is turned on by default and uses
CATALINA_HOME/conf/logging.properties. To be more exact Tomcat does not use
java.util.logging as is but rather will, in the default configuration, replace
the default LogManager implementation with a container friendly implementation
called JULI (extract from http://tomcat.apache.org/tomcat-5.5-doc/logging.html)
The following describes how the default logging (ie java.util.logging) works in
tomcat-5.5 (well, it describes how I saw it working :) ):
I.
When using CATALINA_HOME/conf/logging.properties from the box (ie without any
modifications) all the logging performed in the particular web app goes to the
handlers defined in the .handlers clause, or in other words it gets logged into
the logs/catalina.dateStamp.txt file and the console. In addition, all the
exceptions thrown by the web app go to the 2localhost handler, ie they are
logged into the localhost.dateStamp.log
That's what CATALINA_HOME/conf/logging.properties has:
--
handlers = 1catalina.org.apache.juli.FileHandler, ,
2localhost.org.apache.juli.FileHandler,...
.handlers = 1catalina.org.apache.juli.FileHandler,
java.util.logging.ConsoleHandler
1catalina.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
1catalina.org.apache.juli.FileHandler.prefix = catalina.
2localhost.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
2localhost.org.apache.juli.FileHandler.prefix = localhost.
--
that is what our web app has
--
public class TestServlet extends HttpServlet {
public void doGet(H
{
Logger logger1 = Logger.getLogger(test);
Handler[] handlers = logger1.getHandlers();
for (int i = 0; i handlers.length; i++) {
Handler handler = handlers[i];
System.out.println(handler);
}
System.out.println(handlers.size: + handlers.length);
logger1.info(INFO logging is successful);
throw new IllegalStateException(test exception);
}
}
--
once TestServlet serves HTTP GET request the result is:
a) Console has the following
handlers.size: 0// result of System.out.println
Nov 23, 2005 5:24:37 PM com.SSMB.TestProj.servlets.TestServlet doGet //
result of logging
INFO: INFO logging is successful
b) catalina.2005-11-23.log has the following:
Nov 23, 2005 5:24:37 PM com.SSMB.TestProj.servlets.TestServlet doGet //
result of logging
INFO: INFO logging is successful
c) localhost.2005-11-23.log has the following
java.lang.IllegalStateException: test exception //
result of throwing the ISEx
at
com.SSMB.TestProj.servlets.TestServlet.doGet(TestServlet.java:45)
II.
If we want the logging performed by a particular web app and the exceptions
thrown by it to go to a particular file we can modify
CATALINA_HOME/conf/logging.properties. Let's assume that we have got a web
app that runs on the /test context.
That's how CATALINA_HOME/conf/logging.properties should be modified
--
# add new handler, 6test.org.apache.juli.FileHandler, to the list
handlers =
1catalina.org.apache.juli.FileH,...,6test.org.apache.juli.FileHandler
## new line - 'test' logger will only log into 6test handler
test.handlers=6test.org.apache.juli.FileHandler
...
## define 6test file handler - all logging done via 'test' logger
## will go to test.dateStamp.txt file
6test.org.apache.juli.FileHandler.level = FINE
6test.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
6test.org.apache.juli.FileHandler.prefix = test.
## all of the exceptions coming from /test context are to be logged into 6test
handler.
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/test].level =
INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/test].handlers
= 6test.org.apache.juli.FileHandler
--
once TestServlet (see its doGet method content above) serves HTTP GET request
the result is:
a) Console has the following
[EMAIL PROTECTED] // result of System.out.println
handlers.size: 1// result of
System.out.println
b) test.2005-11-23.log has the following:
Nov 23, 2005 6:17:21 PM com.SSMB.TestProj.servlets.TestServlet doGet //
result of logging
INFO: INFO logging is successful
Nov 23, 2005
