[
https://issues.apache.org/jira/browse/ODE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239137#comment-14239137
]
Sathwik Bantwal Premakumar commented on ODE-1026:
-------------------------------------------------
Igor,
Thanks for reporting the issue.
I don't have the bandwidth to test this issue. I can provide headstart on this.
T1:
deploy
acquired rw[writeLock]
(current execution point of
T1)->retirePriviousPackage->unRegister(waiting for magement[writeLock])
release rw[wrireLock]
loop
fireEvent
fireStateChange
T2:
deploy
acquire rw[writeLock]
retirePriviousPackage->unRegister(acquire magement[writeLock] )
release rw[wrireLock]
loop
(current execution point of T2)->register(acquired
magement[writeLock])->getProcessConfiguration(waiting for rw[readLock])
fireStateChange
As we can see that,
T1 has acquired rw[writeLock] and is waitng for magement[writelock]
T2 has acquired management[writeLock] and is waiting for rw[readlock]
hence the deadlock.
> Deployment deadlock
> -------------------
>
> Key: ODE-1026
> URL: https://issues.apache.org/jira/browse/ODE-1026
> Project: ODE
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 1.3.6
> Reporter: Igor Vorobiov
> Attachments: thread1.txt, thread2.txt
>
>
> There is deadlock when two processes are redeployed at the same time.
> Attached deadlock threads trace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
