Hi Hasitha, Thanks for the confirmation.
Looks like for my requirement, selectors is not the choice. My requirement is to have a queue with messages which can be approved by another party. Need to maintain the queue messages which have not been approved. Possibly the best option would be to use another queue for unapproved messages and keep it untouched. Shazni Nazeer Associate Technical Lead | WSO2 Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com <http://wso2.com/signature> On Mon, Sep 12, 2016 at 5:42 AM, Hasitha Hiranya <hasit...@wso2.com> wrote: > Hi Shazni, > > This is the expected behavior of MB. > Messages will go to DLC if not matched. Things to note here is > > 1. MB does not support selectors cluster-wide (if there is a subscriber > with a matching selector on some other node, sorry) > 2. We cannot keep the message in the queue because of "slot based message > distribution logic" we have. It complicates the slot story. Thus messages > are moved to DLC. > > Is there a possibility for you to use Admin Services to route messages > back to original queue? Even then, if not matched to any subscriber, > messages will get back to DLC. > > Thanks > > On Sun, Sep 11, 2016 at 9:31 PM, Shazni Nazeer <sha...@wso2.com> wrote: > >> Hi all, >> >> I created a queue in WSO2 MB and placed a couple of messages with given >> correlation id's using the management console. And I wrote a sample message >> receiver to receive messages from the queue with a selector matching the >> correlation id. I could successfully retrieve the message. >> >> However, I could also see that the messages which didn't match are moved >> to the dead letter channel (DLC) queue. This is o.k in certain >> circumstances. >> >> I also could find the [1] where the new feature requirement is to delete >> the messages. Therefore moving to DLC seems to be the default behavior. >> >> But what if I want to keep the unmatched messages untouched in the queue >> it self for further processing. Is there a configuration to achieve this? >> Or do we have other means to bring back to the original queue. (Of course >> not by using the management console) >> >> [1] https://wso2.org/jira/browse/MB-1597 >> >> Shazni Nazeer >> Associate Technical Lead | WSO2 >> >> Mob : +94 777737331 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> Blog : http://shazninazeer.blogspot.com >> >> <http://wso2.com/signature> >> > > > > -- > *Hasitha Abeykoon* > Senior Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
