hi people I posted the original thread on this just to clarify, there is just one app server, no clusters.
the site works fine, no problems with sessions at all I was just wondering what would happen if the server had to hold on to these session objects for a much much longer period of time cheers Jens Schumann wrote: >| I don't believe Orion (or other J2EE containers) distribute >| changes to the ServletContext object to other VM/Cluster >| members? > >According to Servlet Spec the ServletContext exists per VM only - and it >states that this is even true in a distributed environment. For global data >you should use EJB or DB instead. So no automatic sharing there. > >| To address these requirements, you'd need to persist the user's >| access date state on a shared resource in your cluster. >| Serialized UserState objects on a shared file system, or a DB table. > >Well - I am still not confident which works best. > >Anyone else any experiences in implementing a clustered global application >context which allows sharing? In my current issue DB and file system aren't >an option - so we currently run an experiment with http servlets listing to >JMS (and write information in the app context and synch them via JMS). >Depending on the app server you run into issues because of non clusterable >JMS Server ... > >Recommendations? > >Jens > > >
