You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Massimiliano Guillaro <m....@gmail.com> on 2011/01/13 12:14:05 UTC

WS-notification via HTTP client problem

Hi,

i use Servicemix Fuse 4.3-fuse-03.00 to implement a publish/subscribe system
using wsn2005 component. i should create this configuration:

Publisher -> Broker (wsn2005) -> Consumer 

Publisher is a java application that uses the broker.wsdl exposed by wsn.xml
example to send notification

Consumer is a java application that uses broker.wsdl to make a subscription
and it is, also, a web service that should receive notification.

Not all work fine, in fact, i can send a notification, i can subscribe to a
topic but i don't receive notification to my web service.

My web service is reached by a normal browser. It has a single stupid web
method "increase" that when someone invokes this method it write "received"
to tomcat console

To eliminate any doubt i did a subscription and notification from soapUI
using http://10.20.64.175:8080/NConsumerService/Consumer?http.soap=true and
also
http://10.20.64.175:8080/NConsumerService/Consumer/increase?http.soap=true
but no Soap arrives to my web service

When i send me a notification by soapUI, the response of the broker is OK
202 and if i see in the jconsole i observe that it dequeue the notification.

What i wrong? Do  i have to change somethings in the wsn.xml example?

I'm newbie so please help me.

Thanks
MG
-- 
View this message in context: http://servicemix.396122.n5.nabble.com/WS-notification-via-HTTP-client-problem-tp3339606p3339606.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: WS-notification via HTTP client problem

Posted by Massimiliano Guillaro <m....@gmail.com>.
Hi Matthieu,
i read the jira bug and i note that it is very similar to my problem. I
write here my log to  confirm it:

11:55:01,200 | WARN  | eMQ Session Task | JmsSubscription                  |
rvicemix.wsn.jms.JmsSubscription  197 | 181 - servicemix-wsn2005 -
2010.02.0.fuse-02-00 | Error notifying consumer
org.apache.servicemix.nmr.api.ServiceMixException: Could not dispatch
exchange. No matching endpoints.
        at
org.apache.servicemix.nmr.core.FlowRegistryImpl.dispatch(FlowRegistryImpl.java:110)[84:org.apache.servicemix.nmr.core:1.3.0.fuse-02-00]
        at
org.apache.servicemix.nmr.core.ChannelImpl.dispatch(ChannelImpl.java:286)[84:org.apache.servicemix.nmr.core:1.3.0.fuse-02-00]
        at
org.apache.servicemix.nmr.core.ChannelImpl.send(ChannelImpl.java:117)[84:org.apache.servicemix.nmr.core:1.3.0.fuse-02-00]
        at
org.apache.servicemix.jbi.runtime.impl.DeliveryChannelImpl.send(DeliveryChannelImpl.java:178)[95:org.apache.servicemix.jbi.runtime:1.3.0.fuse-02-00]
        at
org.apache.servicemix.common.EndpointDeliveryChannel.send(EndpointDeliveryChannel.java:89)[94:servicemix-common:2010.02.0.fuse-02-00]
        at
org.apache.servicemix.wsn.jbi.JbiSubscription.doNotify(JbiSubscription.java:137)[181:servicemix-wsn2005:2010.02.0.fuse-02-00]
        at
org.apache.servicemix.wsn.jms.JmsSubscription.onMessage(JmsSubscription.java:193)[181:servicemix-wsn2005:2010.02.0.fuse-02-00]
        at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1229)[46:org.apache.activemq.activemq-core:5.4.1.fuse-01-00]
        at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134)[46:org.apache.activemq.activemq-core:5.4.1.fuse-01-00]
        at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205)[46:org.apache.activemq.activemq-core:5.4.1.fuse-01-00]
        at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:122)[46:org.apache.activemq.activemq-core:5.4.1.fuse-01-00]
        at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:43)[46:org.apache.activemq.activemq-core:5.4.1.fuse-01-00]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_21]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_21]
        at java.lang.Thread.run(Thread.java:619)[:1.6.0_21]

Are you sure that is a bug or is it a own configuration problem? For me is
difficult to think that a previous version works fine and the new don't work
whereas the code of wsn2005 isn't changed. Sorry for my vent but I am very
frustrated by this.

Thanks for your interest

Regards
Massimiliano
-- 
View this message in context: http://servicemix.396122.n5.nabble.com/WS-notification-via-HTTP-client-problem-tp3339606p3339910.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: WS-notification via HTTP client problem

Posted by Matthieu Cormier <Ma...@concertia.com>.
Hello Massimiliano,

The information in this bug I filed may help:
https://issues.apache.org/jira/browse/SM-2033

I've been able to get WS-notification working on version 3 with some modification to Servicemix due to a bug, but have been unsuccessful in getting ws-notification working in version 4.  Please read the bug description and see if is similar to the problem you are having.

Matthieu


On Jan 13, 2011, at 7:14 AM, Massimiliano Guillaro wrote:

> 
> Hi,
> 
> i use Servicemix Fuse 4.3-fuse-03.00 to implement a publish/subscribe system
> using wsn2005 component. i should create this configuration:
> 
> Publisher -> Broker (wsn2005) -> Consumer 
> 
> Publisher is a java application that uses the broker.wsdl exposed by wsn.xml
> example to send notification
> 
> Consumer is a java application that uses broker.wsdl to make a subscription
> and it is, also, a web service that should receive notification.
> 
> Not all work fine, in fact, i can send a notification, i can subscribe to a
> topic but i don't receive notification to my web service.
> 
> My web service is reached by a normal browser. It has a single stupid web
> method "increase" that when someone invokes this method it write "received"
> to tomcat console
> 
> To eliminate any doubt i did a subscription and notification from soapUI
> using http://10.20.64.175:8080/NConsumerService/Consumer?http.soap=true and
> also
> http://10.20.64.175:8080/NConsumerService/Consumer/increase?http.soap=true
> but no Soap arrives to my web service
> 
> When i send me a notification by soapUI, the response of the broker is OK
> 202 and if i see in the jconsole i observe that it dequeue the notification.
> 
> What i wrong? Do  i have to change somethings in the wsn.xml example?
> 
> I'm newbie so please help me.
> 
> Thanks
> MG
> -- 
> View this message in context: http://servicemix.396122.n5.nabble.com/WS-notification-via-HTTP-client-problem-tp3339606p3339606.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.