Hi,
see also the thread "http sessions drive me nuts" and Jboss-Bug [ jboss-Bugs-709559 ] https://sourceforge.net/tracker/?func=detail&atid=376685&aid=709559&group_id =22866
In my opinion the jetty-out-of-the-Jboss-box is bogus as other systems like jboss-with-tomcat or Bea wls6.2 behave differently with the same war / web-app / distibutable tag. Imho, the default action for jetty should be as for tomcat ..
Heiko,
I have done everything I can to help you with this.
It's quite simple.
If you don't want to use distributable sessions, don't declare your webapp distributable.
If you do, uncomment to section in Jetty's jboss-service.xml and run the 'all' configuration.
If you declare your webapp distributable and run the default configuration the distributable seesion manager along with a number of other components that are hardlinked to javagroups will be instantiated. Javagroups is NOT present in the default config, hence the errors that you see.
By the time the code reaches these errors it is is awkward try to roll back to the standard session manager.
I have not bothered to try to implement this as I feel the time would be better spent elsewhere...
I'm sure that I could misconfigure the tomcat bundle or Bea and get them too to break, but it would be of no significant use to me, when I knew exactly how to configure them correctly.
Next time I go through the code in question, I will see if I can make the behaviour friendlier, but I don't consider it a priority.
that's my last word on the matter,
Jules
-----Original Message----- From: Joao Clemente [mailto:[EMAIL PROTECTED] Sent: Thursday, March 27, 2003 2:03 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] session bug?
On Wed, Mar 26, 2003 at 07:45:55PM -0500, Dan K. wrote:
I believe there is a bug with getting the session in JBoss
3.0.6 using the
"all" configuration with <distributable/> in web.xml. The
behavior is
that every request to my test servlet gets a new session id
(new session
is created).
If I remove the <distributable/> element from web.xml then
it works as
expected, which means the current session is kept and the
id is the same
on each request.
I was actually trying to get session replication in a
clustered setup to
work and found this while investigating. Can anyone verify?
It works at least for simple setups. (I have some weird object on my session that I can't serialize and I can't understand why) Tip: Have you enabled the JGStore in jbossweb.sar?
How is your setup that when you remove the "distributable" you still can
keep session on a lb environment? I'm guessing you're not load balancing
at this time, right?
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
