RE: Issue Running Current Forrest Dev under Tomcat 5
Hi, I'g forwarding your comment to the forrest mail-list as I don't have the answer for you directly. However, Tomcat does start and run. I can access my Forrest webapp as well as the Cocoon webapp. I just can't access the Tomcat Manager or the JSP/Servlet Example/Sample pages, or a couple of other webapps like Xindice or eXist. But Tomcat does startup and deliver at least some of my webapps. - mike -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 8:07 AM To: Tomcat Users List Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi, The reason I ask is because of the commons-logging CNFEs. If commons-logging can't load or initialize itself, Tomcat will basically not start. Yoav Shapira Millennium Research Informatics -Original Message- From: Hare, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 2:11 PM To: 'Tomcat Users List' Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi Yoav, The only log files I find for forrest are located in forrest's WEB-INF/logs directory under webapps. The log files are 9 of them and they are all empty. Other than that I do not know how forrest performs logging. - m -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 12:37 PM To: Tomcat Users List Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi, How does Forrest 0.6 configure (or try to) its logging? Yoav Shapira Millennium Research Informatics -Original Message- From: Hare, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 12:38 PM To: Tomcat Users List Subject: Issue Running Current Forrest Dev under Tomcat 5 Hi, I am coming from the Forrest Mailing List. I noticed that forrest 0.6 was causing a problem when trying to access the Tomcat homepage. I first noticed the problem with Tomcat 5.0.27 (I never tried anything earlier), but it carries through to 5.0.28 and 5.5.1 (I am currently using Windows XP, SunJava 1.5.0 and Tomcat 5.5.1) If I put the WAR file generated by Forrest 0.6 into the webapps dir, Tomcat will unravel the war and I can even access the Forrest site. However if I try to access the Tomcat Homepage (http://mysite.com:8080/index.jsp), the JSP Samples or the Servlet Examples, I get an HTTP:404 error. If I remove the war file and the unraveled webapp and restart Tomcat, I can once again access the Tomcat Homepage. I should say that Forrest 0.5.1 does not cause this behavior with Tomcat. Everything works fine. I have taken several stderr.log snapshots, before the forrest 0.6 installation, with forrest 0.6 installed and with forrest 0.5.1 installed. Right off the bat, starting Tomcat with forrest 0.6 war in webapps causes the stderr.log to grow 130KB rather than 3KB without forrest. The stderr.log is full of various errors: snip Sep 10, 2004 9:49:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Logging Error: Could not set up Cocoon Logger, will use screen instead org.apache.avalon.framework.configuration.ConfigurationException: cannot create FileTarget snip NFO: Cache file root directory: C:\Programs\ApacheGroup\Tomcat5\work\Catalina\localhost\ForrestExample s \coc oon-files Sep 10, 2004 9:49:23 AM org.apache.tomcat.util.digester.Digester endElement SEVERE: End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) snip ep 10, 2004 9:49:23 AM org.apache.catalina.startup.ContextConfig processDefaultWebConfig SEVERE: Parse error in default web.xml org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.j a va:2 746) snip and so on.. These do not appear if forrest 0.6 is not in the picture. Can anyone help me determine the root cause for this problem? Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system
RE: Issue Running Current Forrest Dev under Tomcat 5
Maybe something in the the issue tracking document will help http://issues.cocoondev.org//browse/FOR-277?page=comments#action_11511 I posted the configuration file I use to identify Forrest to Tomcat. It does have a section on logging. However, I have this same problem if I just put the war file in Tomcat's webapps directory and not use the configuration file. - Michael Hare GnuPG Key fingerprint = 1AD4 726D E359 A31D 05BF ACE5 CA93 7AD5 D8E3 A876 -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 8:07 AM To: Tomcat Users List Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi, The reason I ask is because of the commons-logging CNFEs. If commons-logging can't load or initialize itself, Tomcat will basically not start. Yoav Shapira Millennium Research Informatics -Original Message- From: Hare, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 2:11 PM To: 'Tomcat Users List' Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi Yoav, The only log files I find for forrest are located in forrest's WEB-INF/logs directory under webapps. The log files are 9 of them and they are all empty. Other than that I do not know how forrest performs logging. - m -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 12:37 PM To: Tomcat Users List Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi, How does Forrest 0.6 configure (or try to) its logging? Yoav Shapira Millennium Research Informatics -Original Message- From: Hare, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 12:38 PM To: Tomcat Users List Subject: Issue Running Current Forrest Dev under Tomcat 5 Hi, I am coming from the Forrest Mailing List. I noticed that forrest 0.6 was causing a problem when trying to access the Tomcat homepage. I first noticed the problem with Tomcat 5.0.27 (I never tried anything earlier), but it carries through to 5.0.28 and 5.5.1 (I am currently using Windows XP, SunJava 1.5.0 and Tomcat 5.5.1) If I put the WAR file generated by Forrest 0.6 into the webapps dir, Tomcat will unravel the war and I can even access the Forrest site. However if I try to access the Tomcat Homepage (http://mysite.com:8080/index.jsp), the JSP Samples or the Servlet Examples, I get an HTTP:404 error. If I remove the war file and the unraveled webapp and restart Tomcat, I can once again access the Tomcat Homepage. I should say that Forrest 0.5.1 does not cause this behavior with Tomcat. Everything works fine. I have taken several stderr.log snapshots, before the forrest 0.6 installation, with forrest 0.6 installed and with forrest 0.5.1 installed. Right off the bat, starting Tomcat with forrest 0.6 war in webapps causes the stderr.log to grow 130KB rather than 3KB without forrest. The stderr.log is full of various errors: snip Sep 10, 2004 9:49:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Logging Error: Could not set up Cocoon Logger, will use screen instead org.apache.avalon.framework.configuration.ConfigurationException: cannot create FileTarget snip NFO: Cache file root directory: C:\Programs\ApacheGroup\Tomcat5\work\Catalina\localhost\ForrestExample s \coc oon-files Sep 10, 2004 9:49:23 AM org.apache.tomcat.util.digester.Digester endElement SEVERE: End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) snip ep 10, 2004 9:49:23 AM org.apache.catalina.startup.ContextConfig processDefaultWebConfig SEVERE: Parse error in default web.xml org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.j a va:2 746) snip and so on.. These do not appear if forrest 0.6 is not in the picture. Can anyone help me determine the root cause for this problem? Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you
Issue Running Current Forrest Dev under Tomcat 5
Hi, I am coming from the Forrest Mailing List. I noticed that forrest 0.6 was causing a problem when trying to access the Tomcat homepage. I first noticed the problem with Tomcat 5.0.27 (I never tried anything earlier), but it carries through to 5.0.28 and 5.5.1 (I am currently using Windows XP, SunJava 1.5.0 and Tomcat 5.5.1) If I put the WAR file generated by Forrest 0.6 into the webapps dir, Tomcat will unravel the war and I can even access the Forrest site. However if I try to access the Tomcat Homepage (http://mysite.com:8080/index.jsp), the JSP Samples or the Servlet Examples, I get an HTTP:404 error. If I remove the war file and the unraveled webapp and restart Tomcat, I can once again access the Tomcat Homepage. I should say that Forrest 0.5.1 does not cause this behavior with Tomcat. Everything works fine. I have taken several stderr.log snapshots, before the forrest 0.6 installation, with forrest 0.6 installed and with forrest 0.5.1 installed. Right off the bat, starting Tomcat with forrest 0.6 war in webapps causes the stderr.log to grow 130KB rather than 3KB without forrest. The stderr.log is full of various errors: snip Sep 10, 2004 9:49:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Logging Error: Could not set up Cocoon Logger, will use screen instead org.apache.avalon.framework.configuration.ConfigurationException: cannot create FileTarget snip NFO: Cache file root directory: C:\Programs\ApacheGroup\Tomcat5\work\Catalina\localhost\ForrestExamples\cocoon-files Sep 10, 2004 9:49:23 AM org.apache.tomcat.util.digester.Digester endElement SEVERE: End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) snip ep 10, 2004 9:49:23 AM org.apache.catalina.startup.ContextConfig processDefaultWebConfig SEVERE: Parse error in default web.xml org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.java:2746) snip and so on.. These do not appear if forrest 0.6 is not in the picture. Can anyone help me determine the root cause for this problem? Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Issue Running Current Forrest Dev under Tomcat 5
Hi Yoav, The only log files I find for forrest are located in forrest's WEB-INF/logs directory under webapps. The log files are 9 of them and they are all empty. Other than that I do not know how forrest performs logging. - m -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 12:37 PM To: Tomcat Users List Subject: RE: Issue Running Current Forrest Dev under Tomcat 5 Hi, How does Forrest 0.6 configure (or try to) its logging? Yoav Shapira Millennium Research Informatics -Original Message- From: Hare, Michael [mailto:[EMAIL PROTECTED] Sent: Friday, September 10, 2004 12:38 PM To: Tomcat Users List Subject: Issue Running Current Forrest Dev under Tomcat 5 Hi, I am coming from the Forrest Mailing List. I noticed that forrest 0.6 was causing a problem when trying to access the Tomcat homepage. I first noticed the problem with Tomcat 5.0.27 (I never tried anything earlier), but it carries through to 5.0.28 and 5.5.1 (I am currently using Windows XP, SunJava 1.5.0 and Tomcat 5.5.1) If I put the WAR file generated by Forrest 0.6 into the webapps dir, Tomcat will unravel the war and I can even access the Forrest site. However if I try to access the Tomcat Homepage (http://mysite.com:8080/index.jsp), the JSP Samples or the Servlet Examples, I get an HTTP:404 error. If I remove the war file and the unraveled webapp and restart Tomcat, I can once again access the Tomcat Homepage. I should say that Forrest 0.5.1 does not cause this behavior with Tomcat. Everything works fine. I have taken several stderr.log snapshots, before the forrest 0.6 installation, with forrest 0.6 installed and with forrest 0.5.1 installed. Right off the bat, starting Tomcat with forrest 0.6 war in webapps causes the stderr.log to grow 130KB rather than 3KB without forrest. The stderr.log is full of various errors: snip Sep 10, 2004 9:49:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Logging Error: Could not set up Cocoon Logger, will use screen instead org.apache.avalon.framework.configuration.ConfigurationException: cannot create FileTarget snip NFO: Cache file root directory: C:\Programs\ApacheGroup\Tomcat5\work\Catalina\localhost\ForrestExamples \coc oon-files Sep 10, 2004 9:49:23 AM org.apache.tomcat.util.digester.Digester endElement SEVERE: End event threw exception java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) snip ep 10, 2004 9:49:23 AM org.apache.catalina.startup.ContextConfig processDefaultWebConfig SEVERE: Parse error in default web.xml org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger) (Caused by org.apache.commons.logging.LogConfigurationException: java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger (Caused by java.lang.ClassNotFoundException: org.apache.commons.logging.impl.LogKitLogger)) at org.apache.tomcat.util.digester.Digester.createSAXException(Digester.ja va:2 746) snip and so on.. These do not appear if forrest 0.6 is not in the picture. Can anyone help me determine the root cause for this problem? Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
