1. New sessions bounce off an interceptor while the application is being updated. 2. New sessions bypass the interceptor once the application is deployed and ready. 3. Existing sessions are re-vectored by the intereceptor to the old application.
If the existing sessions are not grandfathered, the potential for havoc is pretty high is it not? ----- Original Message ----- From: "Pete Beck" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 28, 2003 6:44 AM Subject: Re: [JBoss-user] Feature idea > Or even better, keep the old application deployed while the new > application is being deployed. > > > On Fri, 2003-02-28 at 13:02, David Corbin wrote: > > The one thing I'd like to see jboss provide. When I an application is > > redeployed, I'd like to see JBoss accept requests for the context of the > > application, and return a page that says "Please try again in a few > > moments". Even better would be some way to configure the response. The > > key point is, that the application is down for a minute, we know that > > it's down for just a bit, we should be able to handle the "error" better. > > > > David > -- > Peter Beck BEng (hons) - Managing Director, Electrostrata Ltd. > http://www.electrostrata.com --+-+-- Experts in e-business and e-commerce > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
