Isn't much more to it but here is the rest, it's happened a couple more
times since my first email to the list, probably about 200 jms messages have
been sent, the majority of them have went through successfully:
javax.jbi.messaging.MessagingException: No component named ID:
10.40.16.154-1177df9603c-0:41 - Couldn't route MessageExcha
nge InOnly[
id: ID:10.40.16.154-1177df9603c-68:0
status: Done
role: consumer
service: {urn://service.notification}feed-jms-service
endpoint: notification
in: <?xml version="1.0" encoding="UTF-8"?><rss xmlns:content="
http://purl.org/rss/1.0/modules/content/"; xmlns:dc="http:
//purl.org/dc/elements/1.1/">
<channel>
... Removed internal message xml since not relevant ...
</channel>
</rss>
]
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(
AbstractFlow.java:175)
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)
That's all I get for the error, doesn't seem overly descriptive.
On Jan 15, 2008 10:20 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> 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/
>
