I'm noticing some strange behaviour with a class that implements
HttpSessionListener and is registered in my apps webapp.xml file as a
listener.
When I call session.getAttribute(xxx) on a session passed into
sessionDestroyed() the thread seems to lock.
I've simplified my class as a test case
PROTECTED]
To: [EMAIL PROTECTED]
Subject: Tomcat 4.0 - HttpSessionListener lockup in sessionDestroyed()
I'm noticing some strange behaviour with a class that implements
HttpSessionListener and is registered in my apps webapp.xml file as a
listener.
When I call session.getAttribute(xxx
Will do
Being somewhat green to Tomcat and the new Servlet API, I just wanted to
make sure I wasn't missing something obvious before officially
considering this as a 'bug'
Craig R. McClanahan wrote:
In order to avoid this problem report getting lost, *please* report it in
our bug
