One second is much too short as most users won't be able to enter data on a web form and click submit :-) but one or two minutes might be more realistic.
However, even with a suitably short timeout, if a user is actively submitting forms or requesting pages, the session will never go away so the server won't go down. If this is a production system, you might try persisting the sessions or go with a cluster with sessions persisted between them with a front-end server (could be apache+mod_jk) that will round-robin requests and automatically direct requests to the box that's up if one goes down. This is a lot of work to configure and run, and my suspicion is this is overkill for your setup :-) -ed On 12/6/05, Ross Gibb <[EMAIL PROTECTED]> wrote: > Your second post seems to contradict your first post. The users are > going to more mad at losing their session or the application entirely? > Do you mean you want the sessions to persist through server restart? I > have no idea if Weblogic supports that. > > A hacky solution off the top of my head would be to set the session > timeout extremely low. Like zero or 1 second, I guess the sessions > wouldn't be around for that long. This solution may have unintended > side effects as many of my hacky solutions do. > > Ross > > > Baker, Russ A wrote: > > >It is Weblogic. I am using a "graceful" shutdown so that if people still > >have open sessions, they can complete what they are doing. The other > >alternative is to force shutdown, but I am afraid I will make enemies if > >I do that... > > > >-----Original Message----- > >From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper > >Sent: Tuesday, December 06, 2005 3:53 PM > >To: user@struts.apache.org > >Subject: Re: Session problem > > > >Baker, Russ A wrote: > > > > > >>Hello, > >> > >>I am trying to figure out how to stop Struts from creating a session. > >>What seems to happen is that once I call an action, a session is > >>created. This is a problem because when I want to gracefully shut down > >>my server, it complains that I still have an active session. Is there > >> > >> > >a > > > > > >>way to configure Struts so that it does not create a session when an > >>action is called? > >> > >> > > > >A session is created the first time something accesses it. Since Struts > >stores various things in session scope, I don't think you can avoid > >having one created. > > > >What container are you using? It seems like an odd behaviour to refuse > >to shut down if there are any active sessions... Are you sure it's > >referring to an HTTP session (as opposed, for example, to a Hibernate > >session or something)? > > > >L. > > > > > >--------------------------------------------------------------------- > >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]
