|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I had this same problem (deadlock between EC2 plugin and JClouds), and looking into it I was able to determine that I could remove the 'synchronized' from the method signature in EC2RetentionStrategy#check(EC2Computer) in the EC2 plugin. Digging into the nested calls, it appears everything is still properly synchronized. We haven't had a problem ever since, and we use the EC2 plugin quite heavily (create ~50 machines a day).