DO NOT REPLY [Bug 4091] - custom host with unpackWARs=true don't expand war automatically - work around fails log4j!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=4091. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=4091 custom host with unpackWARs=true don't expand war automatically - work around fails log4j! [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2004-06-17 21:24 --- I have followed the steps provided to reproduce the bug with TC4.1.30 and with one small mod (need to add .war to the docbase) it works as expected. The complete text I added to sever.xml was: Host name=testhost debug=0 appBase=webapps unpackWARs=true Context path=/myapp docBase=tomcat-docs2.war debug=0/ /Host - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4091] - custom host with unpackWARs=true don't expand war automatically - work around fails log4j!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091 custom host with unpackWARs=true don't expand war automatically - work around fails log4j! [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2003-09-25 16:41 --- As per the documentation (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html) : --- The Document Base (also known as the Context Root) directory for this web application, or the pathname to the web application archive file (if this web application is being executed directly from the WAR file). You may specify an absolute pathname for this directory or WAR file, or a pathname that is relative to the appBase directory of the owning Host. --- When you deploy an application as a war and specify the docBase as a war file name (say tomcat-docs2 or tomcat-docs2.war [ are you supposed to include the extension]) in the server.xml or an [application-name].xml file, the application fails to start with the following exception: java.lang.IllegalArgumentException: Document base ..\webapps\tomcat-docs2.war does not exist or is not a readable directory. This appears to be fixed in the version 5 release (bug 4829). I am running 4.1.27 and although the bug was marked as resolved-fixed, it is still breaking. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4091] - custom host with unpackWARs=true don't expand war automatically - work around fails log4j!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091 custom host with unpackWARs=true don't expand war automatically - work around fails log4j! [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-07-08 15:43 --- as per the above referenced bug 21367, PropertyConfigurator.configure(getServletContext().getResource(/ + getInitParameter(propfile))); solved it! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4091] - custom host with unpackWARs=true don't expand war automatically - work around fails log4j!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091 custom host with unpackWARs=true don't expand war automatically - work around fails log4j! [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] URL||http://nagoya.apache.org/bug ||zilla/show_bug.cgi?id=21367 --- Additional Comments From [EMAIL PROTECTED] 2003-07-07 10:54 --- see also the corresponding log4j bug we posted http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21367 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4091] - custom host with unpackWARs=true don't expand war automatically - work around fails log4j!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091 custom host with unpackWARs=true don't expand war automatically - work around fails log4j! [EMAIL PROTECTED] changed: What|Removed |Added Version|4.0.1 Beta 1|4.1.24 --- Additional Comments From [EMAIL PROTECTED] 2003-07-07 14:15 --- in server.xml, removing the lines (where privalope could well be replaced myapp) Context path=/privaLope docBase=privaLope.war debug=0 cookies=false reloadable=true/ solves two problems: 1) the war files get expanded automatically 2) the context path is no longer null, thus log4j is working again !!! The remaining problem is now: how to tell tomcat not to use cookies !!! Further background: System.out.println(1= +getServletContext().getRealPath(\\)); 1=C:\tomcat\jakarta-tomcat-4.1.24\bin\..\webapps\privaLope\ ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4091] - custom host with unpackWARs=true don't expand war automatically - work around fails log4j!
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4091 custom host with unpackWARs=true don't expand war automatically - work around fails log4j! [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|RESOLVED|REOPENED Resolution|INVALID | Summary|custom host with|custom host with |unpackWARs=true don't |unpackWARs=true don't |expand war automatically|expand war automatically - ||work around fails log4j! --- Additional Comments From [EMAIL PROTECTED] 2003-06-27 15:44 --- We ran into the same problem. Our log4j.properties is located in the top level directory of the war file. Now we get the following error! log4j:ERROR Could not read configuration file [nulllog4j.properties]. java.io.FileNotFoundException: nulllog4j.properties (The system cannot find the file specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:103) at java.io.FileInputStream.init(FileInputStream.java:66) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:300) at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:318) at com.privasphere.privalope.util.Log4JServlet.init(Log4JServlet.java:34) at javax.servlet.GenericServlet.init(GenericServlet.java:256) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:935) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:823) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3420) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3608) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2190) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) log4j:ERROR Ignoring configuration file [nulllog4j.properties]. dataSource = jdbc:mysql://127.0.0.1:3306/privalope log4j:WARN No appenders could be found for logger (Database). log4j:WARN Please initialize the log4j system properly. === any thoughts? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]