[Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pumudu Ruhunage]

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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Hasitha Hiranya]

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  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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pumudu Ruhunage]

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  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  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 
>> 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  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 
 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 
> 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* 
>
>


 --
 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* 
>>>
>>>
>>
>>
>> --
>> *Pamod Sylvester *
>>  *Senior Software Engineer *
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>> email: pa...@wso2.com cell: +94 77 7779495
>>
>
>
>
> --
> *Pamod Sylvester *
>  *Senior Software Engineer *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: pa...@wso2.com cell: +94 77 7779495
>



-- 
Pumudu Ruhunage
Associate Software Engineer | WSO2 Inc
M: +94 779 664493  | http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pamod Sylvester]

Agreed. As you explained its more like a question whether we need to let
the user to reroute to subscribers bound to the same topic or to a
different topic in that case.

As i understood all consumers bound to a topic will receive a given message
and if one of them crashes rerouting it between the consumers in the same
topic will result in a message duplication. It might bring more value IMHO
if we could allow rerouting it to consumers of different topic.

Then again, the question that was triggered was will it affect the
permission model.

Thanks,
Pamod

On Thu, Apr 9, 2015 at 1:23 PM, Ramith Jayasinghe  wrote:

> yes. But think about a situation where for some reason this message
> couldn't be received by the intended subscriber (may be because its crashed
> etc.) but the messages could be of value. So in my point view, its a
> conscious decision/task by user to select what to do with these messages in
> DLC (.e.g user may carefully select to where he wants them to be
> delivered).
>
> On Thu, Apr 9, 2015 at 12:38 PM, Pamod Sylvester  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  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 
>>> 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 
 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 
> 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 
>> 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* 
>>
>>
>
>
> --
> 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* 


>>>
>>>
>>> --
>>> *Pamod Sylvester *
>>>  *Senior Software Engineer *
>>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>>> email: pa...@wso2.com cell: +94 77 7779495
>>>
>>
>>
>>
>> --
>> *Pamod Sylvester *
>>  *Senior Software Engineer *
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>> email: pa...@wso2.com cell: +94 77 7779495
>>
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>


-- 
*Pamod Sylvester *
 *Senior S

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pamod Sylvester]

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  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 
> 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  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 
>>> 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 
 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* 


>>>
>>>
>>> --
>>> 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* 
>>
>>
>
>
> --
> *Pamod Sylvester *
>  *Senior Software Engineer *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: pa...@wso2.com cell: +94 77 7779495
>



-- 
*Pamod Sylvester *
 *Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pamod Sylvester]

+1 showing only the topics in the same hierarchy would be a good option
IMO.

On Thu, Apr 9, 2015 at 1:37 PM, Pumudu Ruhunage  wrote:

> 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  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  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 
>>> 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 
 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 
> 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 
>> 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* 
>>
>>
>
>
> --
> 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* 


>>>
>>>
>>> --
>>> *Pamod Sylvester *
>>>  *Senior Software Engineer *
>>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>>> email: pa...@wso2.com cell: +94 77 7779495
>>>
>>
>>
>>
>> --
>> *Pamod Sylvester *
>>  *Senior Software Engineer *
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>> email: pa...@wso2.com cell: +94 77 7779495
>>
>
>
>
> --
> Pumudu Ruhunage
> Associate Software Engineer | WSO2 Inc
> M: +94 779 664493  | http://wso2.com
>



-- 
*Pamod Sylvester *
 *Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pumudu Ruhunage]

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  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  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* 
>
>


-- 
Pumudu Ruhunage
Associate Software Engineer | WSO2 Inc
M: +94 779 664493  | http://wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Pamod Sylvester]

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  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  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 
>> 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 
>>> 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* 
>>>
>>>
>>
>>
>> --
>> 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* 
>
>


-- 
*Pamod Sylvester *
 *Senior Software Engineer *
Integration Technologies Team, WSO2 Inc.; http://wso2.com
email: pa...@wso2.com cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Ramith Jayasinghe]

yes. But think about a situation where for some reason this message
couldn't be received by the intended subscriber (may be because its crashed
etc.) but the messages could be of value. So in my point view, its a
conscious decision/task by user to select what to do with these messages in
DLC (.e.g user may carefully select to where he wants them to be
delivered).

On Thu, Apr 9, 2015 at 12:38 PM, Pamod Sylvester  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  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 
>> 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  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 
 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 
> 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* 
>
>


 --
 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* 
>>>
>>>
>>
>>
>> --
>> *Pamod Sylvester *
>>  *Senior Software Engineer *
>> Integration Technologies Team, WSO2 Inc.; http://wso2.com
>> email: pa...@wso2.com cell: +94 77 7779495
>>
>
>
>
> --
> *Pamod Sylvester *
>  *Senior Software Engineer *
> Integration Technologies Team, WSO2 Inc.; http://wso2.com
> email: pa...@wso2.com cell: +94 77 7779495
>



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [MB] How to handle reroute operation for durable topic messages in dead letter channel

[Hasitha Hiranya]

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  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 
> 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  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* 
>>
>>
>
>
> --
> 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* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev