Hi Pamod, If 'C' failed to receive a message we should be able to browse the list of internal queues of durable topic subscribers (these queues should be mapped with durable topic names in ui to make them readable) and reroute it only to a given internal queue. Internal queues currently not accessible through in dlc. As i understood this is what hasitha mentioned. This way we don't have to send duplicate durable topic messages to all the subscribers.
I'm not sure how permission model will work in this case. There can be conflicts if permissions are not granted to subscribe/publish to given queue. As a workaround if it's possible, we can only show queues with sufficient permissions to perform reroute operations in ui. Regards, On Thu, Apr 9, 2015 at 12:38 PM, Pamod Sylvester <[email protected]> wrote: > Also another question i have, let's say we're rerouting to among the > consumers of the same topic. i.e for a given topic there're 3 durable > subscriptions(A,B,C), When a message is sent two subscribers receive the > message (A and B) and the message sent to C had failed and sent to the DLC. > > If we reroute the above to A, will it be the case where A received the > same message which was received some time back. > > Thanks, > Pamod > > On Thu, Apr 9, 2015 at 12:32 PM, Pamod Sylvester <[email protected]> wrote: > >> Hi Pumudu, >> >> 1) Will it be the case where we specify the next route based on the >> subscription id ? Also in addition to the current flow, we might need to >> re create/activate a topic entry as well IMO since for durable >> subscriptions we create a queue and a topic entry >> >> 2) Also how with the permission model work in this case ? can there be a >> conflict of rerouting the message to a different subscriber of a different >> role? >> >> Thanks, >> Pamod >> >> On Thu, Apr 9, 2015 at 12:11 PM, Hasitha Hiranya <[email protected]> >> wrote: >> >>> Durable topic has a internal queue. we should be able to browse internal >>> queue. Many people has asked for that feature. >>> >>> >>> >>> On Thu, Apr 9, 2015 at 1:27 AM, Pumudu Ruhunage <[email protected]> wrote: >>> >>>> Hi Hasitha, >>>> >>>> Since this is a durable topic message will it make sense to reroute it >>>> to a queue ? Ideally shouldn't we reroute it to a durable topic, which is >>>> currently not handle by dlc? >>>> >>>> Thanks, >>>> >>>> On Wed, Apr 8, 2015 at 11:21 PM, Hasitha Hiranya <[email protected]> >>>> wrote: >>>> >>>>> Hi Pumudu, >>>>> >>>>> Yes. There will be cases where customers would like this reroute >>>>> function. Make sure to reroute to the same queue for that sub ID. Also, >>>>> make a note that, by the time you reroute, that subscription can be >>>>> "unsubscribed" by user and queue is no longer there. >>>>> >>>>> Thanks >>>>> >>>>> On Wed, Apr 8, 2015 at 11:33 AM, Pumudu Ruhunage <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Currently if a durable topic message didn't receive client >>>>>> acknowledgement from subscriber it will retry 10 times and move that >>>>>> durable topic message to dlc queue. dlc have 3 operations delete, restore >>>>>> and reroute. Out of these, delete and restore operations are functional >>>>>> for >>>>>> durable topic messages in dlc. >>>>>> >>>>>> But problem is that reroute operation only support for queues in dlc. >>>>>> Since dlc can contain durable topic messages, will it be possible to >>>>>> reroute dlc messages to topics as well ? WDYT ? >>>>>> >>>>>> Regards, >>>>>> -- >>>>>> Pumudu Ruhunage >>>>>> Associate Software Engineer | WSO2 Inc >>>>>> M: +94 779 664493 | http://wso2.com >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Hasitha Abeykoon* >>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>>> *cell:* *+94 719363063* >>>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Pumudu Ruhunage >>>> Associate Software Engineer | WSO2 Inc >>>> M: +94 779 664493 | http://wso2.com >>>> >>> >>> >>> >>> -- >>> *Hasitha Abeykoon* >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>> *cell:* *+94 719363063* >>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>> >>> >> >> >> -- >> *Pamod Sylvester * >> *Senior Software Engineer * >> Integration Technologies Team, WSO2 Inc.; http://wso2.com >> email: [email protected] cell: +94 77 7779495 >> > > > > -- > *Pamod Sylvester * > *Senior Software Engineer * > Integration Technologies Team, WSO2 Inc.; http://wso2.com > email: [email protected] cell: +94 77 7779495 > -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
