RE: [Possible bug?] Context configurations and .WAR deployment
Never mind... this was my mistake. It is working just fine. Thanks again, for the help! -Raiden Johnson On Mon, 11 Oct 2004 [EMAIL PROTECTED] wrote: > Actually, I spoke too soon... about it working in production. > > While it's true that the application does load in Tomcat, and everything > is initialized correctly, I can no longer access my application from > Apache via jk2. > > All requests are still making it to Tomcat, but the "/" address space no > longer seems accessible: (like http://www.myserver.com/index.jsp) > > Additionaly, servlets, which were mapped like: > http://www.myserver.com/servlet/TestServlet now throw errors like: > java.lang.NullPointerException > > org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1774) > > org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1575) > > org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860) > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307) > > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) > java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) > > com.net_basic.service.TestServlet.doPost(FetchRecentVisitors.java:30) > > com.net_basic.service.TestServlet.doGet(TestServlet.java:22) > javax.servlet.http.HttpServlet.service(HttpServlet.java:689) > javax.servlet.http.HttpServlet.service(HttpServlet.java:802) > > Any ideas? > > Thank you, > -Raiden Johnson > > > > On Mon, 11 Oct 2004 [EMAIL PROTECTED] wrote: > > > Ok, sounds good. > > > > One thing I noticed with the context.xml, is that it only seems to work > > when it's packaged in a .war file. > > > > However, in development, I am actually deploying a whole ROOT directory > > directly, instead of a packaged .war file. I noticed that when I just > > copied a context.xml into webapps/ROOT/META-INF, tomcat does not seem to > > generate a ROOT.xml file. > > > > I guess for development I can copy context.xml as ROOT.xml directly into > > the tomcat/conf/Catalina/localhost. And then package context.xml in the > > .war file under META-INF for production. > > > > Anyone know why it works this way, though? > > > > Thank you, > > -Raiden > > > > > > > > On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > > > > > You only need to get rid of the cached version if you made changes to it. > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Mon Oct 11 14:05:58 2004 > > > To: Tomcat Users List > > > Subject: RE: [Possible bug?] Context configurations and .WAR deployment > > > > > > Bingo! That worked. Thank you! > > > > > > However, you brought up something that makes a lot more sense to me. I > > > always thought it was strange that I had to have a ROOT.xml outside of the > > > webapp .war file. It makes a whole lot more sense to me to include > > > ROOT.xml in the webapp .war file (under META-INF), and to just get rid of > > > the cached version of ROOT.xml that is generated, when redeploying a new > > > .war file. > > > > > > (Though, you would think that Tomcat would get rid of the cached version > > > on its own.) > > > > > > I think I'm going to change to that method, so that I can keep everything > > > in one .war file. > > > > > > Thank you very much for your help! > > > > > > -Raiden Johnson > > > > > > > > > On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > > > > > > > Try changing the docbase from ROOT TO ROOT.war. > > > > > > > > -Original Message- > > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > > Sent: Mon Oct 11 13:39:17 2004 > > > > To: Tomcat Users List > > > > Subject:RE: [Possible bug?] Context configurations and .WAR deployment > > > > > > > > Hello, > > > > > > > > I will try including what I have in ROOT.xml as context.xml in META-INF, > > > > and then remove the ROOT.xml each time I remove the webapps/ROOT tree to > > > > copy in a new ROOT.war into webapps. > > > > > > > > However, here is what is in my ROOT.xml right now (that is causing the > > > > problem of ROOT.war not being expanded when ROOT.xml is updated): > > >
RE: [Possible bug?] Context configurations and .WAR deployment
Actually, I spoke too soon... about it working in production. While it's true that the application does load in Tomcat, and everything is initialized correctly, I can no longer access my application from Apache via jk2. All requests are still making it to Tomcat, but the "/" address space no longer seems accessible: (like http://www.myserver.com/index.jsp) Additionaly, servlets, which were mapped like: http://www.myserver.com/servlet/TestServlet now throw errors like: java.lang.NullPointerException org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1774) org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1575) org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:860) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307) org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) com.net_basic.service.TestServlet.doPost(FetchRecentVisitors.java:30) com.net_basic.service.TestServlet.doGet(TestServlet.java:22) javax.servlet.http.HttpServlet.service(HttpServlet.java:689) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) Any ideas? Thank you, -Raiden Johnson On Mon, 11 Oct 2004 [EMAIL PROTECTED] wrote: > Ok, sounds good. > > One thing I noticed with the context.xml, is that it only seems to work > when it's packaged in a .war file. > > However, in development, I am actually deploying a whole ROOT directory > directly, instead of a packaged .war file. I noticed that when I just > copied a context.xml into webapps/ROOT/META-INF, tomcat does not seem to > generate a ROOT.xml file. > > I guess for development I can copy context.xml as ROOT.xml directly into > the tomcat/conf/Catalina/localhost. And then package context.xml in the > .war file under META-INF for production. > > Anyone know why it works this way, though? > > Thank you, > -Raiden > > > > On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > > > You only need to get rid of the cached version if you made changes to it. > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Mon Oct 11 14:05:58 2004 > > To: Tomcat Users List > > Subject:RE: [Possible bug?] Context configurations and .WAR deployment > > > > Bingo! That worked. Thank you! > > > > However, you brought up something that makes a lot more sense to me. I > > always thought it was strange that I had to have a ROOT.xml outside of the > > webapp .war file. It makes a whole lot more sense to me to include > > ROOT.xml in the webapp .war file (under META-INF), and to just get rid of > > the cached version of ROOT.xml that is generated, when redeploying a new > > .war file. > > > > (Though, you would think that Tomcat would get rid of the cached version > > on its own.) > > > > I think I'm going to change to that method, so that I can keep everything > > in one .war file. > > > > Thank you very much for your help! > > > > -Raiden Johnson > > > > > > On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > > > > > Try changing the docbase from ROOT TO ROOT.war. > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Mon Oct 11 13:39:17 2004 > > > To: Tomcat Users List > > > Subject: RE: [Possible bug?] Context configurations and .WAR deployment > > > > > > Hello, > > > > > > I will try including what I have in ROOT.xml as context.xml in META-INF, > > > and then remove the ROOT.xml each time I remove the webapps/ROOT tree to > > > copy in a new ROOT.war into webapps. > > > > > > However, here is what is in my ROOT.xml right now (that is causing the > > > problem of ROOT.war not being expanded when ROOT.xml is updated): > > > > > > > > > > > directory="logs" prefix="localhost_log." suffix=".txt" > > > timestamp="true"/> > > > > > > > > > > > > factory > > > org.apache.commons.dbcp.BasicDataSourceFactory > > > > > > > > > maxActive > > > 200 > > > > > > > > > maxIdle > > > 30 > > > > > > > > > maxWait > > > 1 > > > > > &g
RE: [Possible bug?] Context configurations and .WAR deployment
Ok, sounds good. One thing I noticed with the context.xml, is that it only seems to work when it's packaged in a .war file. However, in development, I am actually deploying a whole ROOT directory directly, instead of a packaged .war file. I noticed that when I just copied a context.xml into webapps/ROOT/META-INF, tomcat does not seem to generate a ROOT.xml file. I guess for development I can copy context.xml as ROOT.xml directly into the tomcat/conf/Catalina/localhost. And then package context.xml in the .war file under META-INF for production. Anyone know why it works this way, though? Thank you, -Raiden On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > You only need to get rid of the cached version if you made changes to it. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Mon Oct 11 14:05:58 2004 > To: Tomcat Users List > Subject: RE: [Possible bug?] Context configurations and .WAR deployment > > Bingo! That worked. Thank you! > > However, you brought up something that makes a lot more sense to me. I > always thought it was strange that I had to have a ROOT.xml outside of the > webapp .war file. It makes a whole lot more sense to me to include > ROOT.xml in the webapp .war file (under META-INF), and to just get rid of > the cached version of ROOT.xml that is generated, when redeploying a new > .war file. > > (Though, you would think that Tomcat would get rid of the cached version > on its own.) > > I think I'm going to change to that method, so that I can keep everything > in one .war file. > > Thank you very much for your help! > > -Raiden Johnson > > > On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > > > Try changing the docbase from ROOT TO ROOT.war. > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Mon Oct 11 13:39:17 2004 > > To: Tomcat Users List > > Subject:RE: [Possible bug?] Context configurations and .WAR deployment > > > > Hello, > > > > I will try including what I have in ROOT.xml as context.xml in META-INF, > > and then remove the ROOT.xml each time I remove the webapps/ROOT tree to > > copy in a new ROOT.war into webapps. > > > > However, here is what is in my ROOT.xml right now (that is causing the > > problem of ROOT.war not being expanded when ROOT.xml is updated): > > > > > > > directory="logs" prefix="localhost_log." suffix=".txt" > > timestamp="true"/> > > > > > > > > factory > > org.apache.commons.dbcp.BasicDataSourceFactory > > > > > > maxActive > > 200 > > > > > > maxIdle > > 30 > > > > > > maxWait > > 1 > > > > > > username > > test > > > > > > password > > testpassword > > > > > >driverClassName > >com.mysql.jdbc.Driver > > > > > > url > > > > jdbc:mysql://10.0.0.1:3306/net_basic?autoReconnect=true > > > > > > > > > > > > Thank you, > > -Raiden Johnson > > > > > > > > On Sat, 9 Oct 2004, D'Alessandro, Arthur wrote: > > > > > A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat > > > will create it under your host as ROOT.xml when it is deployed. That > > > doesn't solve the problem your experiencing, what does your ROOT.xml > > > look like? What are you referencing your docBase? Ours word fine by > > > referencing the ROOT.war. > > > > > > Note, if you update the context.xml in your webapp, it doesn't auto > > > update the cached ROOT.xml; you would need to undeploy the webapp, > > > delete the ROOT.xml from conf/Catalina/localhost and redeploy the new > > > webapp. > > > > > > -Original Message- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Saturday, October 09, 2004 3:33 AM > > > To: [EMAIL PROTECTED] > > > Subject: [Possible bug?] Context configurations and .WAR deployment > > > > > > Hello, > > > > > > I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. > > > > > > I am now running into a conflict between ROOT.xml and ROOT.war. > > > > > > This happens when I deploy to production: > > &g
RE: [Possible bug?] Context configurations and .WAR deployment
You only need to get rid of the cached version if you made changes to it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mon Oct 11 14:05:58 2004 To: Tomcat Users List Subject:RE: [Possible bug?] Context configurations and .WAR deployment Bingo! That worked. Thank you! However, you brought up something that makes a lot more sense to me. I always thought it was strange that I had to have a ROOT.xml outside of the webapp .war file. It makes a whole lot more sense to me to include ROOT.xml in the webapp .war file (under META-INF), and to just get rid of the cached version of ROOT.xml that is generated, when redeploying a new .war file. (Though, you would think that Tomcat would get rid of the cached version on its own.) I think I'm going to change to that method, so that I can keep everything in one .war file. Thank you very much for your help! -Raiden Johnson On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > Try changing the docbase from ROOT TO ROOT.war. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Mon Oct 11 13:39:17 2004 > To: Tomcat Users List > Subject: RE: [Possible bug?] Context configurations and .WAR deployment > > Hello, > > I will try including what I have in ROOT.xml as context.xml in META-INF, > and then remove the ROOT.xml each time I remove the webapps/ROOT tree to > copy in a new ROOT.war into webapps. > > However, here is what is in my ROOT.xml right now (that is causing the > problem of ROOT.war not being expanded when ROOT.xml is updated): > > >directory="logs" prefix="localhost_log." suffix=".txt" > timestamp="true"/> > > > > factory > org.apache.commons.dbcp.BasicDataSourceFactory > > > maxActive > 200 > > > maxIdle > 30 > > > maxWait > 1 > > > username > test > > > password > testpassword > > >driverClassName >com.mysql.jdbc.Driver > > > url > > jdbc:mysql://10.0.0.1:3306/net_basic?autoReconnect=true > > > > > > Thank you, > -Raiden Johnson > > > > On Sat, 9 Oct 2004, D'Alessandro, Arthur wrote: > > > A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat > > will create it under your host as ROOT.xml when it is deployed. That > > doesn't solve the problem your experiencing, what does your ROOT.xml > > look like? What are you referencing your docBase? Ours word fine by > > referencing the ROOT.war. > > > > Note, if you update the context.xml in your webapp, it doesn't auto > > update the cached ROOT.xml; you would need to undeploy the webapp, > > delete the ROOT.xml from conf/Catalina/localhost and redeploy the new > > webapp. > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Saturday, October 09, 2004 3:33 AM > > To: [EMAIL PROTECTED] > > Subject: [Possible bug?] Context configurations and .WAR deployment > > > > Hello, > > > > I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. > > > > I am now running into a conflict between ROOT.xml and ROOT.war. > > > > This happens when I deploy to production: > > 1. I delete the ROOT.war and ROOT directory from > > /usr/local/tomcat/webapps > > 2. I delete the ROOT.xml context configuration file in > > /usr/local/tomcat/conf/Catalina/localhost > > 3. I then copy the new ROOT.war file to /usr/local/tomcat/webapps > > 4. I copy the new ROOT.xml file to > > /usr/local/tomcat/conf/Catalina/localhost > > > > This used to work fine in Tomcat 5.0.19. Now, in 5.0.28, when I startup > > the server, I get the following error: > > > > INFO: Missing application web.xml, using defaults only > > StandardEngine[Catalina].StandardHost[localhost].StandardContext[] > > > > And the new ROOT.war file is never expanded (which is why ROOT.xml can't > > find web.xml). > > > > The only way to get the .war file to expand, is to temporarily remove > > the > > ROOT.xml file, startup the server (which then expands the .war file), > > and > > then copy the ROOT.xml file over. > > > > The reason I'm using the ROOT.xml file is to setup DBCP for this webapp > > only. In theory, it's not updated often, but when updates occur, it > > would be copied over during this process, which is why I
RE: [Possible bug?] Context configurations and .WAR deployment
Bingo! That worked. Thank you! However, you brought up something that makes a lot more sense to me. I always thought it was strange that I had to have a ROOT.xml outside of the webapp .war file. It makes a whole lot more sense to me to include ROOT.xml in the webapp .war file (under META-INF), and to just get rid of the cached version of ROOT.xml that is generated, when redeploying a new .war file. (Though, you would think that Tomcat would get rid of the cached version on its own.) I think I'm going to change to that method, so that I can keep everything in one .war file. Thank you very much for your help! -Raiden Johnson On Mon, 11 Oct 2004, D'Alessandro, Arthur wrote: > Try changing the docbase from ROOT TO ROOT.war. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Mon Oct 11 13:39:17 2004 > To: Tomcat Users List > Subject: RE: [Possible bug?] Context configurations and .WAR deployment > > Hello, > > I will try including what I have in ROOT.xml as context.xml in META-INF, > and then remove the ROOT.xml each time I remove the webapps/ROOT tree to > copy in a new ROOT.war into webapps. > > However, here is what is in my ROOT.xml right now (that is causing the > problem of ROOT.war not being expanded when ROOT.xml is updated): > > >directory="logs" prefix="localhost_log." suffix=".txt" > timestamp="true"/> > > > > factory > org.apache.commons.dbcp.BasicDataSourceFactory > > > maxActive > 200 > > > maxIdle > 30 > > > maxWait > 1 > > > username > test > > > password > testpassword > > >driverClassName >com.mysql.jdbc.Driver > > > url > > jdbc:mysql://10.0.0.1:3306/net_basic?autoReconnect=true > > > > > > Thank you, > -Raiden Johnson > > > > On Sat, 9 Oct 2004, D'Alessandro, Arthur wrote: > > > A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat > > will create it under your host as ROOT.xml when it is deployed. That > > doesn't solve the problem your experiencing, what does your ROOT.xml > > look like? What are you referencing your docBase? Ours word fine by > > referencing the ROOT.war. > > > > Note, if you update the context.xml in your webapp, it doesn't auto > > update the cached ROOT.xml; you would need to undeploy the webapp, > > delete the ROOT.xml from conf/Catalina/localhost and redeploy the new > > webapp. > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Saturday, October 09, 2004 3:33 AM > > To: [EMAIL PROTECTED] > > Subject: [Possible bug?] Context configurations and .WAR deployment > > > > Hello, > > > > I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. > > > > I am now running into a conflict between ROOT.xml and ROOT.war. > > > > This happens when I deploy to production: > > 1. I delete the ROOT.war and ROOT directory from > > /usr/local/tomcat/webapps > > 2. I delete the ROOT.xml context configuration file in > > /usr/local/tomcat/conf/Catalina/localhost > > 3. I then copy the new ROOT.war file to /usr/local/tomcat/webapps > > 4. I copy the new ROOT.xml file to > > /usr/local/tomcat/conf/Catalina/localhost > > > > This used to work fine in Tomcat 5.0.19. Now, in 5.0.28, when I startup > > the server, I get the following error: > > > > INFO: Missing application web.xml, using defaults only > > StandardEngine[Catalina].StandardHost[localhost].StandardContext[] > > > > And the new ROOT.war file is never expanded (which is why ROOT.xml can't > > find web.xml). > > > > The only way to get the .war file to expand, is to temporarily remove > > the > > ROOT.xml file, startup the server (which then expands the .war file), > > and > > then copy the ROOT.xml file over. > > > > The reason I'm using the ROOT.xml file is to setup DBCP for this webapp > > only. In theory, it's not updated often, but when updates occur, it > > would be copied over during this process, which is why I do it in my > > deployment script. > > > > What happened since Tomcat 5.0.19 to make it not expand the ROOT.war > > archive at the same time that it's processing a new ROOT.xml file? > > > > Thank you, > > -Raiden Johnson > > > > -
RE: [Possible bug?] Context configurations and .WAR deployment
Try changing the docbase from ROOT TO ROOT.war. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mon Oct 11 13:39:17 2004 To: Tomcat Users List Subject:RE: [Possible bug?] Context configurations and .WAR deployment Hello, I will try including what I have in ROOT.xml as context.xml in META-INF, and then remove the ROOT.xml each time I remove the webapps/ROOT tree to copy in a new ROOT.war into webapps. However, here is what is in my ROOT.xml right now (that is causing the problem of ROOT.war not being expanded when ROOT.xml is updated): factory org.apache.commons.dbcp.BasicDataSourceFactory maxActive 200 maxIdle 30 maxWait 1 username test password testpassword driverClassName com.mysql.jdbc.Driver url jdbc:mysql://10.0.0.1:3306/net_basic?autoReconnect=true Thank you, -Raiden Johnson On Sat, 9 Oct 2004, D'Alessandro, Arthur wrote: > A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat > will create it under your host as ROOT.xml when it is deployed. That > doesn't solve the problem your experiencing, what does your ROOT.xml > look like? What are you referencing your docBase? Ours word fine by > referencing the ROOT.war. > > Note, if you update the context.xml in your webapp, it doesn't auto > update the cached ROOT.xml; you would need to undeploy the webapp, > delete the ROOT.xml from conf/Catalina/localhost and redeploy the new > webapp. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Saturday, October 09, 2004 3:33 AM > To: [EMAIL PROTECTED] > Subject: [Possible bug?] Context configurations and .WAR deployment > > Hello, > > I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. > > I am now running into a conflict between ROOT.xml and ROOT.war. > > This happens when I deploy to production: > 1. I delete the ROOT.war and ROOT directory from > /usr/local/tomcat/webapps > 2. I delete the ROOT.xml context configuration file in > /usr/local/tomcat/conf/Catalina/localhost > 3. I then copy the new ROOT.war file to /usr/local/tomcat/webapps > 4. I copy the new ROOT.xml file to > /usr/local/tomcat/conf/Catalina/localhost > > This used to work fine in Tomcat 5.0.19. Now, in 5.0.28, when I startup > the server, I get the following error: > > INFO: Missing application web.xml, using defaults only > StandardEngine[Catalina].StandardHost[localhost].StandardContext[] > > And the new ROOT.war file is never expanded (which is why ROOT.xml can't > find web.xml). > > The only way to get the .war file to expand, is to temporarily remove > the > ROOT.xml file, startup the server (which then expands the .war file), > and > then copy the ROOT.xml file over. > > The reason I'm using the ROOT.xml file is to setup DBCP for this webapp > only. In theory, it's not updated often, but when updates occur, it > would be copied over during this process, which is why I do it in my > deployment script. > > What happened since Tomcat 5.0.19 to make it not expand the ROOT.war > archive at the same time that it's processing a new ROOT.xml file? > > Thank you, > -Raiden Johnson > > - > 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]
RE: [Possible bug?] Context configurations and .WAR deployment
Hello, I will try including what I have in ROOT.xml as context.xml in META-INF, and then remove the ROOT.xml each time I remove the webapps/ROOT tree to copy in a new ROOT.war into webapps. However, here is what is in my ROOT.xml right now (that is causing the problem of ROOT.war not being expanded when ROOT.xml is updated): factory org.apache.commons.dbcp.BasicDataSourceFactory maxActive 200 maxIdle 30 maxWait 1 username test password testpassword driverClassName com.mysql.jdbc.Driver url jdbc:mysql://10.0.0.1:3306/net_basic?autoReconnect=true Thank you, -Raiden Johnson On Sat, 9 Oct 2004, D'Alessandro, Arthur wrote: > A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat > will create it under your host as ROOT.xml when it is deployed. That > doesn't solve the problem your experiencing, what does your ROOT.xml > look like? What are you referencing your docBase? Ours word fine by > referencing the ROOT.war. > > Note, if you update the context.xml in your webapp, it doesn't auto > update the cached ROOT.xml; you would need to undeploy the webapp, > delete the ROOT.xml from conf/Catalina/localhost and redeploy the new > webapp. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Saturday, October 09, 2004 3:33 AM > To: [EMAIL PROTECTED] > Subject: [Possible bug?] Context configurations and .WAR deployment > > Hello, > > I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. > > I am now running into a conflict between ROOT.xml and ROOT.war. > > This happens when I deploy to production: > 1. I delete the ROOT.war and ROOT directory from > /usr/local/tomcat/webapps > 2. I delete the ROOT.xml context configuration file in > /usr/local/tomcat/conf/Catalina/localhost > 3. I then copy the new ROOT.war file to /usr/local/tomcat/webapps > 4. I copy the new ROOT.xml file to > /usr/local/tomcat/conf/Catalina/localhost > > This used to work fine in Tomcat 5.0.19. Now, in 5.0.28, when I startup > the server, I get the following error: > > INFO: Missing application web.xml, using defaults only > StandardEngine[Catalina].StandardHost[localhost].StandardContext[] > > And the new ROOT.war file is never expanded (which is why ROOT.xml can't > find web.xml). > > The only way to get the .war file to expand, is to temporarily remove > the > ROOT.xml file, startup the server (which then expands the .war file), > and > then copy the ROOT.xml file over. > > The reason I'm using the ROOT.xml file is to setup DBCP for this webapp > only. In theory, it's not updated often, but when updates occur, it > would be copied over during this process, which is why I do it in my > deployment script. > > What happened since Tomcat 5.0.19 to make it not expand the ROOT.war > archive at the same time that it's processing a new ROOT.xml file? > > Thank you, > -Raiden Johnson > > - > 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]
RE: [Possible bug?] Context configurations and .WAR deployment
A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat will create it under your host as ROOT.xml when it is deployed. That doesn't solve the problem your experiencing, what does your ROOT.xml look like? What are you referencing your docBase? Ours word fine by referencing the ROOT.war. Note, if you update the context.xml in your webapp, it doesn't auto update the cached ROOT.xml; you would need to undeploy the webapp, delete the ROOT.xml from conf/Catalina/localhost and redeploy the new webapp. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, October 09, 2004 3:33 AM To: [EMAIL PROTECTED] Subject: [Possible bug?] Context configurations and .WAR deployment Hello, I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. I am now running into a conflict between ROOT.xml and ROOT.war. This happens when I deploy to production: 1. I delete the ROOT.war and ROOT directory from /usr/local/tomcat/webapps 2. I delete the ROOT.xml context configuration file in /usr/local/tomcat/conf/Catalina/localhost 3. I then copy the new ROOT.war file to /usr/local/tomcat/webapps 4. I copy the new ROOT.xml file to /usr/local/tomcat/conf/Catalina/localhost This used to work fine in Tomcat 5.0.19. Now, in 5.0.28, when I startup the server, I get the following error: INFO: Missing application web.xml, using defaults only StandardEngine[Catalina].StandardHost[localhost].StandardContext[] And the new ROOT.war file is never expanded (which is why ROOT.xml can't find web.xml). The only way to get the .war file to expand, is to temporarily remove the ROOT.xml file, startup the server (which then expands the .war file), and then copy the ROOT.xml file over. The reason I'm using the ROOT.xml file is to setup DBCP for this webapp only. In theory, it's not updated often, but when updates occur, it would be copied over during this process, which is why I do it in my deployment script. What happened since Tomcat 5.0.19 to make it not expand the ROOT.war archive at the same time that it's processing a new ROOT.xml file? Thank you, -Raiden Johnson - 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]
[Possible bug?] Context configurations and .WAR deployment
Hello, I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. I am now running into a conflict between ROOT.xml and ROOT.war. This happens when I deploy to production: 1. I delete the ROOT.war and ROOT directory from /usr/local/tomcat/webapps 2. I delete the ROOT.xml context configuration file in /usr/local/tomcat/conf/Catalina/localhost 3. I then copy the new ROOT.war file to /usr/local/tomcat/webapps 4. I copy the new ROOT.xml file to /usr/local/tomcat/conf/Catalina/localhost This used to work fine in Tomcat 5.0.19. Now, in 5.0.28, when I startup the server, I get the following error: INFO: Missing application web.xml, using defaults only StandardEngine[Catalina].StandardHost[localhost].StandardContext[] And the new ROOT.war file is never expanded (which is why ROOT.xml can't find web.xml). The only way to get the .war file to expand, is to temporarily remove the ROOT.xml file, startup the server (which then expands the .war file), and then copy the ROOT.xml file over. The reason I'm using the ROOT.xml file is to setup DBCP for this webapp only. In theory, it's not updated often, but when updates occur, it would be copied over during this process, which is why I do it in my deployment script. What happened since Tomcat 5.0.19 to make it not expand the ROOT.war archive at the same time that it's processing a new ROOT.xml file? Thank you, -Raiden Johnson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
