You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Ryan Moquin <fr...@gmail.com> on 2008/01/15 16:12:55 UTC
(Unknown)
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
Re:
Posted by Ryan Moquin <fr...@gmail.com>.
Actually, I would like to use an injected resource, but I'm not sure how I
would do that from a spring pojo that is injected into my bean. I tried
injecting the context, but it didn't seem to pick it up. More than likely I
was looking at the wrong page to figure out how I should configure it, or
confusing other methods of doing it, such as with the cxf services. I think
I've only tried injecting the context, maybe I should be using the resource
annotation to inject the Delivery Channel, that is probably what would
work. I don't think I've tried it. I'll see if I can get that to work.
On Jan 15, 2008 10:37 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> Yeah, I agree the error is not very descriptive.
> Maybe the problem comes from using the client api inside servicemix-bean.
> You should be able to use an injected DeliveryChannel that may work
> better.
> Or use a synchronous call from the client inside servicemix-bean. I'm
> thinking the client is closed and destroyed before the DONE status comes
> back.
>
> On Jan 15, 2008 4:25 PM, Ryan Moquin <fr...@gmail.com> wrote:
>
> > 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 <gn...@gmail.com> 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 <fr...@gmail.com> 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/
> > >
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
Re:
Posted by Guillaume Nodet <gn...@gmail.com>.
Yeah, I agree the error is not very descriptive.
Maybe the problem comes from using the client api inside servicemix-bean.
You should be able to use an injected DeliveryChannel that may work better.
Or use a synchronous call from the client inside servicemix-bean. I'm
thinking the client is closed and destroyed before the DONE status comes
back.
On Jan 15, 2008 4:25 PM, Ryan Moquin <fr...@gmail.com> wrote:
> 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 <gn...@gmail.com> 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 <fr...@gmail.com> 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/
> >
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re:
Posted by Ryan Moquin <fr...@gmail.com>.
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 <gn...@gmail.com> 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 <fr...@gmail.com> 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/
>
Is this achievable?
Posted by ma...@uk.bnpparibas.com.
hello all,
i am currently exploring the possibility to use servicemix for my
application.
One of the candidate component for servicemix is a code that receives XML
messages, parses them and produces
a set of SQL statements., (let's call it XML parser client, which produces
an xmlparserclient.jar)
As i am still exploring possibility of using servicemix or something else,
i was wondering if this was possible:
- package my own XMLParserClient with my own unit test and so in my own
jar
- later on, if i will go for servicemix, write my own ServiceEngine that
uses XMLClient from this jar
now, i know it looks like a silly question.... but i was wondering, at
runtime, where shall i place my xmlparserclient.jar?
in <servicemixdir>\lib?
shall i package the jar in my serviceunit?
what i want to achieve is to have my own 'candidate servicemix components'
unit tested on their own.
then if i move to servicemix, i can test servicemix componetn as well as
write integration tests for the 'whole architecture';..
anyone could comment?
thanks in advance and regards
marco
This communication is confidential, may be privileged and is meant only for the intended recipient. If you are
not the intended recipient, please notify the sender by reply and delete this message from your system. Any
unauthorised dissemination, distribution or copying hereof is prohibited.
BNP Paribas Fund Services UK Limited, BNP Paribas Trust Corporation UK Limited, BNP Paribas UK Limited,
BNP Paribas Commodity Futures Ltd and Investment Fund Services Limited are authorised and regulated by
the Financial Services Authority.
BNP Paribas, BNP Paribas Securities Services and BNP Paribas Private Bank are authorised by the CECEI
and AMF. BNP Paribas London Branch, BNP Paribas Securities Services London Branch and BNP Paribas
Private Bank London Branch are regulated by the Financial Services Authority for the conduct of their UK
business. BNP Paribas Securities Services London Branch is also a member of the London Stock Exchange.
Re:
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <fr...@gmail.com> 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/
Re:
Posted by Ryan Moquin <fr...@gmail.com>.
Once I used the injected DeliveryChannel (instead of servicemix client) from
my bean (I have to manually pass it around to other classes since I can't
inject it into other classes through spring), the jms notifications don't
give me that error anymore.
Now I just need to figure out how to handle the servicemix-jms components
blocking after a certain amount of messages are sent.
On Jan 15, 2008 4:55 PM, Ryan Moquin <fr...@gmail.com> wrote:
> Actually you know, this sounds like the error described on this page,
> except that the release I'm using (3.2.1) shouldn't have this issue
> anymore:
>
> http://servicemix.apache.org/servicemix-bean.html
>
> Disclaimer
>
> In versions 3.1 to 3.1.2 the ServiceMix Bean component will not handle
> asynchronous messages correctly because the final send of the message marked
> as DONE back to the NMR will be handled as a consumer message and that fails
> because there is no corresponding provider message. The only workaround is
> to send the messages synchronously. Note: This was resolved in 3.1.3,
> 3.2.x and later via SM-1110
> <https://issues.apache.org/activemq/browse/SM-1110>.
>
> So maybe I need to try just sending synchronously then or something... I
> don't know why it wouldn't work correctly.
>
> On Jan 15, 2008 11:52 AM, Daryl Richter < ngzax@comcast.net> wrote:
>
> > Ryan-
> >
> > On Jan 15, 2008, at 10:12 AM, Ryan Moquin 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
> > >
> >
> > As you can see from the status above, this is the just the "reply"
> > Done message exchange indicating that the provider received your
> > message. Do you code like the following in your onMessageExchange()
> > method?
> >
> > if( messageExchange.getStatus() == ExchangeStatus.ACTIVE ) ...
> >
> > before you do any work on it?
> >
> >
> > >
> > > 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
> >
> > --
> > Daryl
> > http://itsallsemantics.com
> >
> >
> >
>
Re:
Posted by Ryan Moquin <fr...@gmail.com>.
Actually you know, this sounds like the error described on this page, except
that the release I'm using (3.2.1) shouldn't have this issue anymore:
http://servicemix.apache.org/servicemix-bean.html
Disclaimer
In versions 3.1 to 3.1.2 the ServiceMix Bean component will not handle
asynchronous messages correctly because the final send of the message marked
as DONE back to the NMR will be handled as a consumer message and that fails
because there is no corresponding provider message. The only workaround is
to send the messages synchronously. Note: This was resolved in 3.1.3,
3.2.xand later via
SM-1110 <https://issues.apache.org/activemq/browse/SM-1110>.
So maybe I need to try just sending synchronously then or something... I
don't know why it wouldn't work correctly.
On Jan 15, 2008 11:52 AM, Daryl Richter <ng...@comcast.net> wrote:
> Ryan-
>
> On Jan 15, 2008, at 10:12 AM, Ryan Moquin 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
> >
>
> As you can see from the status above, this is the just the "reply"
> Done message exchange indicating that the provider received your
> message. Do you code like the following in your onMessageExchange()
> method?
>
> if( messageExchange.getStatus() == ExchangeStatus.ACTIVE ) ...
>
> before you do any work on it?
>
>
> >
> > 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
>
> --
> Daryl
> http://itsallsemantics.com
>
>
>
Re:
Posted by Ryan Moquin <fr...@gmail.com>.
Since it's InOnly, there shouldn't be a reply though. At least that's how I
thought it worked. Once I fire off the message, I don't do anything other
than continue on with the next set of processing. When I get these errors,
I do not see the jms topic enqueue count increment. It may have been a
fluke, but it doesn't appear that the jms message shows up at the topic when
I get this error.
On Jan 15, 2008 11:52 AM, Daryl Richter <ng...@comcast.net> wrote:
> Ryan-
>
> On Jan 15, 2008, at 10:12 AM, Ryan Moquin 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
> >
>
> As you can see from the status above, this is the just the "reply"
> Done message exchange indicating that the provider received your
> message. Do you code like the following in your onMessageExchange()
> method?
>
> if( messageExchange.getStatus() == ExchangeStatus.ACTIVE ) ...
>
> before you do any work on it?
>
>
> >
> > 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
>
> --
> Daryl
> http://itsallsemantics.com
>
>
>
Re:
Posted by Daryl Richter <ng...@comcast.net>.
Ryan-
On Jan 15, 2008, at 10:12 AM, Ryan Moquin 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
>
As you can see from the status above, this is the just the "reply"
Done message exchange indicating that the provider received your
message. Do you code like the following in your onMessageExchange()
method?
if( messageExchange.getStatus() == ExchangeStatus.ACTIVE ) ...
before you do any work on it?
>
> 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
--
Daryl
http://itsallsemantics.com