Issue 133: Concurrency Control
http://code.google.com/p/mobicents/issues/detail?id=133
Comment #6 by vladimir.ralev:
Quick update:
As per the last discussion we agreed to refactor the dispatchers in order
to isolate
session assignment into a common place to avoid handling each dispatcher
separately,
however this wasn't such a good idea because almost all dispatcher have
difference
logic for this and further CancelDispatcher needs special handling (cancel
requests
must not wait the previous request because after the INVITE is processed
there would
be no point of the cancel).
So I plugged the thread-spawn in each dispatcher separately by keeping the
code
structure almost the same as soon as the sip and app sessions are assigned
and i
think that's enough for concurrency to work properly.
I added another two executors - in app session (for app session concurrecy
control)
and one threadpoolcache executor in the sipappdispatcher (for CANCEL and no
concurrency control mode). The concurrency control mode is configurable
from the
SipAppDispatcher MBean interface.
Tests are stil TODO.
Issue attribute updates:
Status: Fixed
Owner: vladimir.ralev
Labels: -Sip-Servlets-Milestone-0.5 Sip-Servlets-Milestone-0.7
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
