Hi Chathura, When message is gone through Axis2FlexibleMEPClient it partially cloned underlying axis2MessageContext and set all the endpoint specific data to that cloned MC and register a callback for send it to BE .It may be a reason for change the MID. Why we need a to store message context externally?
I think this may add up huge memory overhead if message store keeps growing (for high concurrent scenarios and responses are too late to arrive) thanks On Tue, Mar 17, 2015 at 1:21 PM, Chathura Priyankara <chathu...@wso2.com> wrote: > Hi, > > I'm working on my fast track training project [1]. I have to implement > http status code support for FailoverEndpoint. For the re-sending purposes > the original request message context needs to be cloned and store using > the message ID as the reference. The message cloning should be done in the > FailoverEndpoint based on the synapse configuration. > > IMO the original request id changes to a new one after it sent from the > FailoverEndpoint at the Axis2FlexibleMEPClient level. > > Is this correct or I'm missing something here ? > > [1] https://redmine.wso2.com/issues/3725 > > Thanks. > Best Regards. > > -- > Chathura Priyankara > Software Engineer | WSO2 Inc. > Mobile : +94718795340 > Blog : www.codeoncloud.blogspot.com > -- Best Regards Isuru Ranawaka M: +94714629880 Blog : http://isurur.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
