search

harshsxn / jss7

Automatically exported from code.google.com/p/jss7
0 stars 2 forks source link

Possible deadlock in TCAP stack #301

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Possible deadlock when:

From the first thread:
- synchronized InvokeImpl.setState(...) ***
-> DialogImpl.operationEnded(InvokeImpl tcInvokeRequestImpl)
-> this.dialogLock.lock(); ***

From the second stack:
- DialogImpl.processEnd()
-> this.dialogLock.lock(); ***
-> DialogImpl.release() 
-> synchronized InvokeImpl.setState(...) ***

So we have two lockers (this.dialogLock.lock() and synchronized 
InvokeImpl.setState())
Let's remove the second one and

Original issue reported on code.google.com by serg.vet...@gmail.com on 15 Jul 2013 at 3:54

GoogleCodeExporter commented 9 years ago 
Let's remove the second one and use "this.dialogLock.lock()" everywhere

Original comment by serg.vet...@gmail.com on 15 Jul 2013 at 3:56

GoogleCodeExporter commented 9 years ago 
Fixed now:

https://code.google.com/p/jss7/source/detail?r=1ab9167f12bcc9d2dac74cf48604eb40d
eea40fb
(this bug and some little update)

Original comment by serg.vet...@gmail.com on 15 Jul 2013 at 5:01

GoogleCodeExporter commented 9 years ago

Original comment by amit.bha...@gmail.com on 3 Nov 2013 at 12:10

GoogleCodeExporter commented 9 years ago

Original comment by amit.bha...@gmail.com on 3 Nov 2013 at 12:19