[brian.stansberry]

Thanks, Dave, for that news. Very helpful to know you're not seeing a bug in our session handling.

[jsblake]

We're actually seeing instances of this as well, and its a big concern.  We're running JBoss 4.0.5 on several app servers, in a non-clustered configuration.  There is no session sharing/federation between servers.  There is a single web server instance fronting each app server (1-to-1), and a load balancer in front of those.

I don't think we directly use or view session IDs in our code, though I'm certainly going to look thoroughly.

The only time we've seen this happen was shortly after a jboss server restart, but it has happened to 5 or 6 users within a 24 hour period, which I think rules out the possibility of a freak occurrence.  Are there any known bugs in JBoss 4.0.5 that might be the cause of this behavior?

[davewebb]

Joshua,

The issue on our end was with instance variables in our servlets (which are not thread safe).  I would double check that you do not have any instance variables in any servlets or objects that your servlets extend.  Good luck.

[arj_gov]

Hi Brian,

I'm seeing instances of this behavior as well.

I'm running multiple instances of JBOSS 4.0.5 GA on several physical machines, in a clustered configuration. I do not use <distributable> tag in my web.xml's.

I'm using ATG to support session sharing between multiple WAR files.

As said in the earlier posts, this behavior is very random and we r unable to replicate this in our UAT environment.

Please help us.

Regards,

arj_gov

[andigit]

I don't know if this is related but I have seen wrong pages (from old request) being served up to the user. Making it look like the session is crossing. In most cases the user would get wrong page completely.

In our case it was our apache config... don't remember 100% on what we did to fix it. However, I do remember it had something to do with our mod_ajp_proxy's timeout/disablereuse setting, combined with slow servlet and high load.

Thought i would share.