On 02/16/10 02:09 PM, glassfish_at_javadesktop.org wrote:
> I'm getting the same error (see below) when I "redeploy" a stand-alone web module (or an enterprise app with that web module). However, for this error to happen, my sun-web.xml has to include this line: <session-manager persistence-type="file">. If persistence-type is "memory", then I can redeploy almost OK. "Almost", because states of http sessions are not preserved/restored when I want that. I know that my app is built correctly, because when I use persistence-type="file" in sun-web.xml, the sessions are preserved and restored OK when the server is restarted.
>
By default, any HTTP sessions are preserved during server restarts.
You do not have to provide any special configuration (in sun-web.xml)
for this.
See my blog at
http://blogs.sun.com/jluehe/entry/how_to_disable_persisting_of
for how to disable this default behaviour.
On the other hand, by default, any sessions of an application will be
destroyed
during the application's undeployment or redeployment. See my blog at
http://blogs.sun.com/jluehe/entry/retain_session_data_during_redeployment
to learn how HTTP sessions may be preserved during a redeployment.
Hope this helps.
Jan
> I use GlassFish v3 on Linux.
>
> ERROR:
>
> Virtual server [server] already has a web module [mymod] loaded at [/mymod]; therefore web module [mymod] cannot be loaded at this context path on this virtual server.
> [Message sent by forum member 'javjav' (visualitems_at_gmail.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=387068
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>