Open GoogleCodeExporter opened 9 years ago
I have some news:
It seems the problem happens with tomcat 7 but not with jetty 6.
I'm wondering if it's not the behavior of the servlet3 specification which
doen' force the same thread to handle a request for all its lifetime. Maybe a
thread creates a session and onother tries to terminate it. If the scenario
happens between two threads and two sessions we have two dead locks.
Do you think it's a possibility???
Original comment by zhamdi.into
on 5 Mar 2012 at 6:06
Original issue reported on code.google.com by
zhamdi.into
on 5 Mar 2012 at 4:44