users@glassfish.java.net

Re: GlassFish V3 planning - What do *you* want in GlassFish V3?

From: Jerome Dochez <Jerome.Dochez_at_Sun.COM>
Date: Fri, 02 Nov 2007 10:26:58 -0700

yes we have identified this requirement, it's called suspend where the
requests would be queued at low level and wait for the "redeployment"
to be finished. in theory, we would not even have to say anything to
the user (assuming there are not too many outstanding requests), it
would just take a bit longer to be serviced.

would that help ?

On Nov 2, 2007, at 10:06 AM, glassfish_at_javadesktop.org wrote:

> I would like to be able to be able to easily put an application on
> "stand by" with a (configurable) "down for maintenance -- coming
> back soon" message when I need to redeploy an application, or do
> some other maintenance. Basically have the container put the
> application offline, without being rude to the users. Right now you
> need to jump through a bunch of hoops to get that to work.
>
> If you have to take the container down, well, then you're stuck --
> but the goal seems to be that the container is a long running piece
> of software, so that's why I think this functionality should be
> rolled in to the container rather than be the individual
> applications responsibility. There should not be a clustering
> requirement for this as well.
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=243525
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>