Hi Hasitha, I assume this is only related to durable subscribers. So to handle this, there should be a logical implementation to uniquely identify a durable subscriber when it shuts down and later on in the future reconnects, then it can decide what messages to send to it while it was not running. JMS does that by a combination of the clientID and the durable subscriber name.
Thanks, On Tue, Nov 25, 2014 at 6:11 PM, Hasitha Hiranya <[email protected]> wrote: > Hi, > > There is an identified concern on the $Subject. > > We are saving topic messages to durable store to share the messages across > the nodes and prevent OOM. > > Consider following scenario > > 1. Sub1 >> subscribes to topic1 on MB1 node > 2. Sub2 >> subscribes to topic1 on MB1 node > 3. Sub3 >> subscribes to topic1 on MB1 node > > Sub1 closes. > We cannot delete messages as messages are shared by all subscribers for > topic1 (Sub2 and Sub3 are still alive) > > Now > > Sub4 >> subscribes to topic1 on MB1 node > > It will get above mentioned messages which we did not delete (we just send > message to all relevant subs on the node). > > But as per topic behavior this should not happen. What would be possible > solutions for this? In MB 2.2.0, we did not get this problem as messages > were fire-and-forget (without considering acks, but in MB 3.0.0 we consider > acks for topic messages). > > What would be the possible solutions? > > Thanks > -- > *Hasitha Abeykoon* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Malith Dhanushka Software Engineer - Data Technologies *WSO2, Inc. : wso2.com <http://wso2.com/>* *Mobile* : +94 716 506 693
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
