[
https://issues.apache.org/jira/browse/SANDESHA2-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gatford resolved SANDESHA2-98.
-------------------------------------
Resolution: Fixed
> Avoid thread context switch in RMS sending strategy
> ---------------------------------------------------
>
> Key: SANDESHA2-98
> URL: https://issues.apache.org/jira/browse/SANDESHA2-98
> Project: Sandesha2
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Paul Fremantle
>
> We can optimize the performance of the RMS by sending the current message on
> the current thread (if possible)
> A message is to be sent by the RMS. There is no user transaction (this is a
> precondition).
> Update the message number and (in the case where this is an RM1.0 with replay
> happening) decide if this is the next message in order (i.e. all previous
> messages are acknowledged).
> Execute and Store the message, and insert the sender bean. Commit
> Now, If ((there is no User Tran) And (Replay is off, OR this is the next
> message in order))
> { commit the storage, add sequence header and then send }
--
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]
