[INT-3070] MongoDbMessageStore cannot read delayed messages - Spring JIRA

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Critical
Resolution: Complete
Affects Version/s: 2.2.4
Fix Version/s: 2.2.5, 3.0 M3
Component/s: MongoDB Support
Labels:
- PullRequest
- mongodb

Description

When MongoDbMessageStore is used as message store for delayer it fails to read messages from MongoDB.

Delayer is wrapping GenericMessage into DelayHandler.DelayedMessageWrapper, and MongoDbMessageStore is warping this again to MongoDbMessageStore.MessageWrapper. In the database there are MongoDbMessageStore.MessageWrapper -> DelayHandler.DelayedMessageWrapper -> GenericMessage -> Payload.

MongoDbMessageStore.MessageReadingMongoConverter does not provide special handling for DelayHandler.DelayedMessageWrapper as it done for MongoDbMessageStore.MessageWrapper. And because DelayHandler.DelayedMessageWrapper stores GenericMessage without default constructor, MongoDbMessageStore.MessageReadingMongoConverter fails to read it from MongoDB.

Attachments

Issue Links

depends on

INT-3049 DelayedMessageWrapper should be public in order to access the wrapped message from infrastructure code

Closed

Options

Sub-Tasks

1.	Ensure Message conversion for MongoDbMessageStore in case of within payload	Closed	Artem Bilan
2.	Ensure that Delayer works correctly with RedisMessageStore	Closed	Artem Bilan
3.	Ensure that Delayer works correctly with GemfireMessageStore	Closed	Artem Bilan

Activity

People

Assignee:: Artem Bilan

Reporter:: Roman Leicht

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 25/Jun/13 5:08 PM

Updated:: 05/Sep/13 10:22 AM

Resolved:: 03/Sep/13 3:48 PM