Well I think I solved a work around the problem.
It seems that an MDB in the system they had put some code
to set the jaas environment and call login on the module.
Removing this and using the unauthenticatedIdentity in the real module
allowed the cache cleanup to not affect anything. But I believe
After trying to get a stack trace of where the logout is coming from
I have this problem now showing up in the jms database access.
Which seems to be the same problem with cache invalidating subject.
I do have a stack trace showing that the logout is coming from the cache flushing.
Any ideas on fix
I have been working on a SecurityException that happens about 30 minutes into a stress
test. The stress test basically keeps getting a bean
and invoking a method on that bean. Works great for about 30 minutes.
Then it fails. It isn't doing anything different at the 30 minute mark. I turned on
jbo
