"First in First Out" of QueueChannel is ineffective when use JDBC message-store [INT-2544]

[spring-operator]

Shawn Guo opened INT-2544 and commented

please refer to the http://forum.springsource.org/showthread.php?125898-Disordered-MessageGroupQueue.

Amol Nayak has analyzed the causes of this issue.

---

Affects: 2.1 GA

Reference URL: http://forum.springsource.org/showthread.php?125898-Disordered-MessageGroupQueue

This issue is a sub-task of #6523

[spring-operator]

Oleg Zhurakousky commented

The problem is actually in the fact that we are missing a field which should stay unchanged throughout the life of a Message.
Both CREATE_DATE and UPDATE_DATE are currently correct. CREATE_DATE - the time of the inception of the MG and UPDATE_DATE is the timestamp when this MG was updated the last time. What we need is MESSAGE_ADDED_DATE which wil be set only once during the time when message is initially added to the group and than remain constant so we can do ORDER BY MESSAGE_ADDED_DATE

[spring-operator]

Gary Russell commented

How about, instead of setting the UPDATE_DATE on all rows to the group update date; use the UPDATE_DATE of the newest row as the group update date and then the UPDATE_DATE would be the natural order and rows would remain in FIFO order.

It still doesn't help with in-memory databases where you might have more than one row in a millisecond, but folks could use a queue channel for testing. An in-memory database doesn't add value in production.

[spring-operator]

Oleg Zhurakousky commented

Moved it to M2 since after several discussions we realized that we actually need to fix the DB schema to fix it right.