]
Clebert Suconic commented on JBMESSAGING-1431:
----------------------------------------------
We had a quick chat about this issue on IRC today:
Revisit paged messages during transactions
------------------------------------------
Key: JBMESSAGING-1431
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1431
Project: JBoss Messaging
Issue Type: Task
Reporter: Clebert Suconic
Assignee: Clebert Suconic
Fix For: 2.0.0 Beta
During transactions, a paged message goes towards the memory, while non-paged towards
routing.
If paging goes on and off during long running transactions (waiting an user decision),
the message on the transaction could be delivered out of order, as paging was turned on
and off during the transaction.
To fix that we need to find an uniform way.
The best way probably is to keep everything in memory (but discounting the sizes from
PagingManager to avoid an OME) until commit is called.
The testcase for this should play with turning paging on in the middle of a
transaction... sending a message, turning it of while another consumer produces/consumes
messages, sending more messages.. and validating the order.
The second thread should not be blocked. If we add messages on paging during the
transaction we will need to block depage until the commit arrives and that would be a
problem when the commit is waiting an user event (click or anything like that) causing
long running transactions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: