Its not the session, its the shared Subject. Since you say this occurs with caching disabled I need a testcase to verify what is going on. Create a bug report on sourceforge with an example ear or as much detail as possible.
http://sourceforge.net/tracker/?group_id=22866&atid=376685
Bug report created.
Arnold,
I have also been experiencing this same problem except on JBoss 4.0.0 and 4.0.1RC1:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=56217
The problem was occurring when I had both the ClientLoginModule and UserRolesLoginModule in my application-policy. This is consistent with the theory that the problem is a result of a race condition I guess. I have solved the problem by removing the ClientLoginModule from my application-policy.
What does your application-policy look like?
Hi robbutera,
I too use ClientLoginModule and UsersRolesLoginModule, but using JBoss 3.2.4.
I have experienced this problem when login credential cache is disabled. Did you disable yours too?
Cheers.