RE: Updating running WARs?
I use the Tomcat Deployer. If you're not familiar with Tomcat Deployer you'll be able to find information here. http://jakarta.apache.org/tomcat/tomcat-5.0-doc/deployer-howto.html In a nutshell, it's a collection of ant (ant.apache.org) tasks that will deploy a war to a remote tomcat server. But I had some JNDI issues unless my context was defined inside the META-INF/context.xml file I spoke of. -Original Message- From: David Wood [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 12:51 PM To: tomcat-user@jakarta.apache.org Subject: RE: Updating running WARs? I'm sorry, I'm confused. Once you created a context.xml in your WARs, what were your steps to update a running application? "Mitchell K. McCuiston" <[EMAIL PROTECTED]> wrote on 02/07/2005 10:40:18 AM: > Try configuring your app context inside of the META-INF/context.xml inside > of your war instead of your server.xml. I had the same problem and this > seemed to fix it. > > -Original Message- > From: David Wood [mailto:[EMAIL PROTECTED] > Sent: Friday, February 04, 2005 3:15 PM > To: tomcat-user@jakarta.apache.org > Subject: Updating running WARs? > > > What's the "right way" to update a running WAR in Tomcat 5.5? > > Is there anything resembling the manager's "reload" feature for WARs? Or > are we forced to remove the context via the manager and then re-add a new > context back in? (Or restart Tomcat?) > > I've been searching through documentation for the manager, and then > looking a bit at the source code, and it seems like it's impossible to > reload a context unless it's exploded. > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Updating running WARs?
I'm sorry, I'm confused. Once you created a context.xml in your WARs, what were your steps to update a running application? "Mitchell K. McCuiston" <[EMAIL PROTECTED]> wrote on 02/07/2005 10:40:18 AM: > Try configuring your app context inside of the META-INF/context.xml inside > of your war instead of your server.xml. I had the same problem and this > seemed to fix it. > > -Original Message- > From: David Wood [mailto:[EMAIL PROTECTED] > Sent: Friday, February 04, 2005 3:15 PM > To: tomcat-user@jakarta.apache.org > Subject: Updating running WARs? > > > What's the "right way" to update a running WAR in Tomcat 5.5? > > Is there anything resembling the manager's "reload" feature for WARs? Or > are we forced to remove the context via the manager and then re-add a new > context back in? (Or restart Tomcat?) > > I've been searching through documentation for the manager, and then > looking a bit at the source code, and it seems like it's impossible to > reload a context unless it's exploded. > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Updating running WARs?
Try configuring your app context inside of the META-INF/context.xml inside of your war instead of your server.xml. I had the same problem and this seemed to fix it. -Original Message- From: David Wood [mailto:[EMAIL PROTECTED] Sent: Friday, February 04, 2005 3:15 PM To: tomcat-user@jakarta.apache.org Subject: Updating running WARs? What's the "right way" to update a running WAR in Tomcat 5.5? Is there anything resembling the manager's "reload" feature for WARs? Or are we forced to remove the context via the manager and then re-add a new context back in? (Or restart Tomcat?) I've been searching through documentation for the manager, and then looking a bit at the source code, and it seems like it's impossible to reload a context unless it's exploded. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Updating running WARs?
On Fri, 04 Feb 2005 17:45:12 -0600, Jonathan Wilson <[EMAIL PROTECTED]> wrote: > Someone else will be able to attest to this better than I, but there is > a known issue with the classloader [I think] that doesn't release memory > on a undeploy..eventually you'll run out of memory after a certain > number of deploy/undeploys. You could try using the jvm's -Xmx modifier > in your startup/catalina shell, which may buy you more time[guru input > here, please]... Do you mean this ? http://issues.apache.org/bugzilla/show_bug.cgi?id=26135 It turned out to be a JDK feature ;) > But my app starts up lightweight so I can schedule downtime a couple of > hours or so in advance, then drop tomcat for a few minutes while I > deploy manually. Maybe you could use the Manager: Stop the Service, > undeploy, stop TC, start TC, deploy the service using the Manager, start > service if necessary. It is indeed difficult to guarantee that everything will be cleaned up, unless the application is reasonably well written. In case of issues like usage of the bean instrospector as mentioned above, some explicit cleanup is required (now done automatically by Tomcat, but this will only be in the next release). See the bug report for info on workarounds. -- x Rémy Maucherat Developer & Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Updating running WARs?
Someone else will be able to attest to this better than I, but there is a known issue with the classloader [I think] that doesn't release memory on a undeploy..eventually you'll run out of memory after a certain number of deploy/undeploys. You could try using the jvm's -Xmx modifier in your startup/catalina shell, which may buy you more time[guru input here, please]... But my app starts up lightweight so I can schedule downtime a couple of hours or so in advance, then drop tomcat for a few minutes while I deploy manually. Maybe you could use the Manager: Stop the Service, undeploy, stop TC, start TC, deploy the service using the Manager, start service if necessary. Just my .02 For more info search the archives...it's come up more than a few times since I've been on this list. --Jonathan Wendy Smoak wrote: From: "David Wood" <[EMAIL PROTECTED]> are we forced to remove the context via the manager and then re-add a new context back in? (Or restart Tomcat?) This is how I've always done it-- remove and install. (For added fun... I removed and installed a webapp repeatedly yesterday, and after about the sixth time, Tomcat died with an OutOfMemory error. Has anyone else had this happen? I chalked it up to the JVM on HP-UX being weird again, but decided to avoid doing that on the production server in the future.)
Re: Updating running WARs?
From: "David Wood" <[EMAIL PROTECTED]> > are we forced to remove the context via the manager and then re-add a new > context back in? (Or restart Tomcat?) This is how I've always done it-- remove and install. (For added fun... I removed and installed a webapp repeatedly yesterday, and after about the sixth time, Tomcat died with an OutOfMemory error. Has anyone else had this happen? I chalked it up to the JVM on HP-UX being weird again, but decided to avoid doing that on the production server in the future.) -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Updating running WARs?
Besides 'Hot Patching' (placing an updated class or jsp on the application runtime) I have not found a way to do what you are trying to find. >>> [EMAIL PROTECTED] 02-04-2005 14:15 >>> What's the "right way" to update a running WAR in Tomcat 5.5? Is there anything resembling the manager's "reload" feature for WARs? Or are we forced to remove the context via the manager and then re-add a new context back in? (Or restart Tomcat?) I've been searching through documentation for the manager, and then looking a bit at the source code, and it seems like it's impossible to reload a context unless it's exploded. - 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]
Updating running WARs?
What's the "right way" to update a running WAR in Tomcat 5.5? Is there anything resembling the manager's "reload" feature for WARs? Or are we forced to remove the context via the manager and then re-add a new context back in? (Or restart Tomcat?) I've been searching through documentation for the manager, and then looking a bit at the source code, and it seems like it's impossible to reload a context unless it's exploded. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
