[
https://issues.apache.org/jira/browse/SANDESHA2-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551478
]
Thomas McKiernan commented on SANDESHA2-129:
--------------------------------------------
Another potential use of a non-locking cursor (if we decide to go down that
route) is in the getNextMsgToSend processing.
Here we currently do a find across the whole table, just to chose one bean to
send.
The find could not lock, we could get the sender and return it. The
SenderWorker could then retrieve that message in order to lock it for the send.
> StorageManager improvements
> ---------------------------
>
> Key: SANDESHA2-129
> URL: https://issues.apache.org/jira/browse/SANDESHA2-129
> Project: Sandesha2
> Issue Type: Improvement
> Reporter: Thomas McKiernan
> Attachments: chmhmupload.patch, lockingIterator.patch
>
>
> Some aspects of the storage manager design could do with some looking at.
> Specifically I'm thinking of:
> performance improvements in the inMemory design
> improved documentation
> Any other thoughts?
--
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]
