HI Akalanka, One possible option might be we cold keep track of the message id which was generated when the message originated and define that as an attribute of AndesMessageMetaData, so that when we retrieve or reroute the messages from DLC we could generate a new message id for its meta information, when we retrieve the message content we could refer to the reference we kept under AndesMessageMetaData.
This is one option, however there could be performance constraints to it since we we will have to do an additional look-up. Thanks, Pamod On Tue, Dec 16, 2014 at 10:49 AM, Akalanka Pagoda Arachchi < [email protected]> wrote: > > Hi all, > > I am working on [1]. > > When message broker 3.0.0 restores message from the dead letter channel, > although messages are restored, they will never get redelivered since > message delivery is handled by a slot based mechanism which will not > process an already processed message. > > As I can see with the current implementation, the only possible way to > re-route a dead message through MB is to consider it as a new message and > forward it through message incoming logic. This requires retrieving old > message content from the database and re-inserting as new message content > while deleting the old content. > > This is heavy work. Any ideas on this? > > [1] - https://wso2.org/jira/browse/MB-871 > > -- > *Darshana Akalanka Pagoda Arachchi,* > *Software Engineer* > *078-4721791 <078-4721791>* > -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: [email protected] cell: +94 77 7779495
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
