[
https://issues.apache.org/jira/browse/SANDESHA2-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Lovett resolved SANDESHA2-49.
----------------------------------
Resolution: Fixed
> Add locking to the in-memory storage manager
> --------------------------------------------
>
> Key: SANDESHA2-49
> URL: https://issues.apache.org/jira/browse/SANDESHA2-49
> Project: Sandesha2
> Issue Type: Improvement
> Reporter: Matt Lovett
> Attachments: deadlock3.patch, deadlock4.patch, deadlock5.patch,
> deadlockAck.patch, deadlockAck2.patch, detectSandeshaDeadlock.patch,
> lock.patch, lock2.patch, outSeqId.patch
>
>
> The beans held by the in-memory storage manager are not goverened by adequate
> locking. This leads to lots of potential holes - for example if 2 reliable
> messages arrive very close together we could mess up the sequence ack ranges.
> A general solution seems to be to lock each bean on first access, and release
> it when the sandesha transaction ends.
> I'll attach a patch that implements this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
