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.
