[
https://issues.apache.org/jira/browse/ODE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570853#comment-14570853
]
Sathwik Bantwal Premakumar commented on ODE-1026:
-------------------------------------------------
Igor,
How about enclosing the loop containing fireEvent and fireStateChange within
rw(readLock). This should order the lock acquisition and avoid the deadlock.
{panel:borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
*acquire rw(readLock)*
loop
fireEvent
fireStateChange
*release rw(readLock)*
{panel}
Can you check with this change and let us know?
> 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)
