After I have subscribed several topics, is there a way to ask WSN2005 what are all my subscribed topics?
gnodet wrote: > > Could you raise a JIRA for this problem ? > As you said, it should not alter the behavior of the unsubscribe > request, but the reason is that the endpoint is destroyed before the > exchange comes back from the HTTP component, thus leading to this > problem. It should have no effects beyond this log statement. > > On Fri, Sep 12, 2008 at 8:45 PM, kai0411 <[EMAIL PROTECTED]> > wrote: >> >> Sorry, my bad. Every subscription is for a particular topic. So >> 'unsubscribe' >> this subscription means 'unsubscribe' this topic. Am I right? >> >> Another issue. After send 'un-subscription' request, I got 'status 200' >> back, and JMX confirmed my 'unsubscription' works. But Servicemix console >> reported this error: >> >> 2008-09-12 13:29:52,538 ERROR - WSNComponent - Error >> setting exchange status to ERROR >> javax.jbi.messaging.MessagingException: illegal call to send / sendSync >> at >> org.apache.servicemix.jbi.messaging.MessageExchangeImpl.handleSend(MessageExchangeImpl.java:614) >> at >> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:385) >> at >> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:431) >> at >> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:58) >> at >> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610) >> at >> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170) >> at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167) >> at >> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) >> at java.lang.Thread.run(Thread.java:595) >> >> >> >> gnodet wrote: >>> >>> The unsubscribe is related to a subscription. You can't unsubscribe >>> from a topic directly afaik, you need to give the reference to the >>> subscription to this very topic. >>> >>> On Fri, Sep 12, 2008 at 8:32 PM, kai0411 <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> thanks for the answer. how about 'unsubscribe' to a specified topic "my >>>> topic"? >>>> >>>> >>>> gnodet wrote: >>>>> >>>>> I think the unsubscribe request corresponding to the scenario would >>>>> be: >>>>> >>>>> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; >>>>> xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2"; >>>>> xmlns:wsa="http://www.w3.org/2005/08/addressing";> >>>>> <env:Header> >>>>> <wsa:To> >>>>> >>>>> http://servicemix.org/wsnotification/Subscription/ID-some-host-38972-1188922931357-3-1 >>>>> </wsa:To> >>>>> </env:Header> >>>>> <env:Body> >>>>> <wsnt:Unsubscribe /> >>>>> </env:Body> >>>>> </env:Envelope> >>>>> >>>>> Note that the wsa:To content comes from the SubscribeResponse. >>>>> >>>>> On Fri, Sep 12, 2008 at 6:37 PM, kai0411 <[EMAIL PROTECTED]> >>>>> wrote: >>>>>> >>>>>> It was given a message format to 'subscribe' an endpoint for a topic >>>>>> in >>>>>> http://servicemix.apache.org/example-scenario.html. >>>>>> What is the format to 'un-subscribe' an endpoint? >>>>>> I tried tags <Unsubscribe> and <unSubscribe>, but got 'HTTP 500' >>>>>> error. >>>>>> >>>>>> >>>>>> >>>>>> gnodet wrote: >>>>>>> >>>>>>> This is the default behaviour if you don't use a PulPoint. When you >>>>>>> register a subscription, you give the address of the JBI endpoint in >>>>>>> the request so that the broker can send you notifications on the >>>>>>> specified topic. >>>>>>> >>>>>>> On Thu, Sep 4, 2008 at 6:36 PM, kai0411 <[EMAIL PROTECTED]> >>>>>>> wrote: >>>>>>>> >>>>>>>> there is example in >>>>>>>> http://servicemix.apache.org/example-scenario.html >>>>>>>> for a >>>>>>>> 'Pull' notification. Users have to 'pull' their notification from >>>>>>>> the >>>>>>>> Broker. >>>>>>>> How to implement a 'Push' notification, ie. when WSN2005 gets a >>>>>>>> notification, it would 'push' the notification to a service engine? >>>>>>>> >>>>>>>> thanks for help >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Servicemix-wsn2005-tp19314625p19314625.html >>>>>>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Cheers, >>>>>>> Guillaume Nodet >>>>>>> ------------------------ >>>>>>> Blog: http://gnodet.blogspot.com/ >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Servicemix-wsn2005-tp19314625p19459687.html >>>>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Cheers, >>>>> Guillaume Nodet >>>>> ------------------------ >>>>> Blog: http://gnodet.blogspot.com/ >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Servicemix-wsn2005-tp19314625p19461717.html >>>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >>>> >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Guillaume Nodet >>> ------------------------ >>> Blog: http://gnodet.blogspot.com/ >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/Servicemix-wsn2005-tp19314625p19461944.html >> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Servicemix-wsn2005-tp19314625p19519865.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
