Hi Kasun, +1. Not supporting this is a current limitation of our MS/MP implementation. Specially, when it comes to worker/manager deployments, we do not have full control over deployed message processors in a clustered environment.
>From MS/MP's point of view, each message processor has its own JMS session and consumer objects which allows it to run independently from other message processors. In addition, we have already tested multiple message processors with no issues. Therefore, AFAIU, I don't see any complications (from MS/MP's point of view). All we have to do is add a coordination layer on top of the existing message processor implementation to achieve the aforementioned objective. On Tue, Jul 1, 2014 at 5:20 AM, Kasun Indrasiri <[email protected]> wrote: > Hi, > > We need to support $subject. As we support coordination for ESB tasks > through ntask integration, we can use the same concept to execute the > message processor tasks too. > > The main objective is to execute a message processor on an elected worker > node in a given cluster deployment. > > @Shafreen/Ishan : Any thoughts on the complexities involved with this. > > Thanks, > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > -- Regards, *Shafreen* Software Engineer WSO2 Inc Mobile : 077-556-395-1
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
