The code itself seems good. Do you have a more complete stack trace to
understand where the exception is sent from ?
On Jan 15, 2008 4:12 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> Can anyone explain why this error would occur?
>
> javax.jbi.messaging.MessagingException: No component named ID:
> 10.40.16.154-1177df9603c-0:1 - Couldn't route MessageExchange InOnly[
> id: ID:10.40.16.154-1177df9603c-28:0
> status: Done
> role: consumer
> service: {urn://service.notification}feed-jms-service
> endpoint: notification
>
>
> The situation is that I have a servicemix-bean deployment with a bean that
> fires everything 15 seconds using quartz. Notifications are generated and
> sent to a jms service and then to a topic. When I start everything up,
> the
> first notification seems to go correctly to the jms service, the next 2
> give
> the above error, then it goes back to successfully sending to the jms
> service. Sporadically I'll get error like the above if I let it run. I
> haven't seemed to have this problem when sending from a cxf service. My
> xbean.xml hasn't changed, though my code has changed a little for sending
> to
> the jms service. Is this a code issue?
>
> The code I am using is:
>
> destinationQname = new QName(getDestinationNamespace(),
> getDestinationService());
> Source feedItemSource = getMarshaller().marshal(feedItem);
> InOnly exchange = client.createInOnlyExchange();
> NormalizedMessage message = exchange.getInMessage();
> message.setContent(feedItemSource);
> exchange.setService(destinationQname);
> client.send(exchange);
>
> It really is pretty standard and seems to work 90% of the time, I just
> don't
> understand why this error seems to pop up the other 10%.
>
> Thanks,
> Ryan
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
