timing problems between messageReceived() and the timeout task
--------------------------------------------------------------
Key: ASYNCWEB-33
URL: https://issues.apache.org/jira/browse/ASYNCWEB-33
Project: Asyncweb
Issue Type: Bug
Components: Client
Affects Versions: client-1.0.0
Reporter: Sangjin Lee
Assignee: Sangjin Lee
The progress of the timeout task and that of messageReceived() are fully
concurrent. There are a couple of interesting problems. First, if the timeout
task launches and in the meantime the messageReceived() method fires, it is
possible for messageReceived() to interrupt the timeout task thread.
The investigation of this issue led to the discovery of another timing-related
issue. Namely, if the timeout task launches and in the meantime the
messageReceived() method fires, it is possible for messageReceived() to cache
the session back into the cache (although the timeout task will try to close
the connection later on) so that there is a small window of opportunity that
the connection will be checked out for another request. This might cause
unexpected session closings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
