Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-SLEE SubComponent-SLEE-Core
Version-2.2.1 Release-Type-FINAL SLEE-2.2.1.FINAL
New issue 2067 by tom.uijldert: SLEE not compliant with JSLEE 1.1, par.
8.6.6 (concurrency control)
http://code.google.com/p/mobicents/issues/detail?id=2067
Version tested: 2.2.0
Bug Description:
Refer to Sbb object "-64fae1f1:12c16b31fb8:-7f13" in the attached server
log.
At some point, a "disconnect()" routine is called through its local
interface that initiates a BYE.
The Response to that event is fired in a different thread and handled in
parallel, causing the NPE at line 1052.
At line 993, a BYE is sent and the connectionstate changes to STOP (line
1004).
After receiving the response in line 1014, said Sbb is activated in
parallel and the state hasn't changed (line 1048).
This is not in accordance with par. 8.6.6 of the JSLEE spec which states
that all methods of an Sbb object would be invoked serially.
Is this correct or am I overlooking something?
Attachments Required: The DEBUG Console log.
Test-case may be to create an Sbb that offers a local interface
method "disconnect()" that sends a BYE on an established SIP dialog whereby
the response is generated very quickly.
A "Thread.yield()" in the disconnect() method just after sending the BYE to
slow things down might help in reproducing the problem.
Hope this helps,
Tom.
Attachments:
NoConcurrencyServer.log 131 KB
