You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "Mike L." <pa...@hotmail.com> on 2011/03/21 20:45:36 UTC
InOut over JMS always leads to Timout (ExchangeTimedOutException)
All:
I have been trying to take advantage of the InOut pattern over JMS. I am using Camel 2.4.0 and ActiveMQ 5.3.1
I have created a simple example that can be run to replicate the problem I am experiencing. Attached please find the source code plus ant build file. Within the libs folder is a file listing all required jars (sorry - I wasn't sure about uploading a 30M file to this list!).
Once you have the necessary jars in place under libs/compile then in two terminal windows:
ant clean run-consumer
ant run-publisher
The consumer implements the InOut processor and the publisher invokes it over JMS.
Within the second terminal window you will soon see
[java] Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis. Exchange[Message: John]
[java] at org.apache.camel.component.jms.JmsProducer.processInOut(JmsProducer.java:265)
[java] at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:147)
Originally I had specified 5 consumers in the metadata/test-env/res/applicationContext-consumer.xml file. However, I can set the number of consumers down to one and the same problem occurs. BTW, we use a clustered environment - so I would like to specify multiple consumers and use multiple computers.
Any insight into this would be greatly appreciated!!
TIA,
Mike L. (aka patzerbud)
Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Mike,
gerne doch ;-)
Am 22.03.2011 16:13, schrieb Mike L.:
>
> In the real world application - I tried to simplify it so as to
> replicate/demonstrate that a problem exists - I implemented a Processor
> because the message has several values set in Headers. I am aware of
> Camel's excellent automatic conversion of the payload (as in your
> example) but I am not aware of how to also declare and access any
> Header properties without access to the Exchange.
>
You can use annotations to get the headers but in the case using
exchange may be a good thing.
>
>> The next thing is you do not need to use inOut jms and activemq components use InOut by default. To call the bean simply use:
>>
>> <to uri="myBean"/>
>>
>> and define the bean in spring:
>>
>> <bean id="myBean" class="MyProcessor"/>
> The client application runs on a separate machine from the server. Additionally, I do not want the client applications to have to "know" the bean that processes the requests; but rather only the endpoint name. I had hoped to be able to make synchronous calls over JMS because it somehow feels more loosely coupled (although, it could be argued that knowing the endpoint name still makes it point-to-point).
>
> Forgive me if I misunderstood your point.
What I wanted to say is that you do not have to do anything special to
make a synchronous call. If your client sends to the queue like you do
with requestBody then it initiates a synchronous call. It sends to the
specified queue and creates a temp queue for the reply which it gives
the server using the replyTo header in jms. On the server side you do:
<from uri="jms:myQueue"/>
<to uri="myBean"/>
That is all you need to receive the jms message, process it in the bean
and send the reply back.
Christian
--
----
http://www.liquid-reality.de
RE: AW: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
Christian:
Vielen Dank fuer Deine Antwort! Aber (jetzt auf Englisch) please see my comments, inline:
> To: users@camel.apache.org
> Date: Tue, 22 Mar 2011 09:12:16 +0100
> Subject: AW: InOut over JMS always leads to Timout (ExchangeTimedOutException)
>
> Hi,
>
> I have no yet really run your example but I have successfully run similar examples so camel should be able to do what you want to achieve here.
>
> Some ideas how your code can be made simpler. For the processor you should use the bean features of camel. Simply create your processor like this:
>
> class MyProcessor {
> public String doStuff(String inMsg) {
> return "hello " + inMsg;
> }
> }
>
> This does the same as your code.
In the real world application - I tried to simplify it so as to
replicate/demonstrate that a problem exists - I implemented a Processor
because the message has several values set in Headers. I am aware of
Camel's excellent automatic conversion of the payload (as in your
example) but I am not aware of how to also declare and access any
Header properties without access to the Exchange.
>
> The next thing is you do not need to use inOut jms and activemq components use InOut by default. To call the bean simply use:
>
> <to uri="myBean"/>
>
> and define the bean in spring:
>
> <bean id="myBean" class="MyProcessor"/>
The client application runs on a separate machine from the server. Additionally, I do not want the client applications to have to "know" the bean that processes the requests; but rather only the endpoint name. I had hoped to be able to make synchronous calls over JMS because it somehow feels more loosely coupled (although, it could be argued that knowing the endpoint name still makes it point-to-point).
Forgive me if I misunderstood your point.
Thanks again,
Mike L. (aka patzerbud)
>
> This should work nicely.
>
> Christian
>
> Von: Mike L. [mailto:patzerbud@hotmail.com]
> Gesendet: Montag, 21. März 2011 20:46
> An: users@camel.apache.org
> Betreff: InOut over JMS always leads to Timout (ExchangeTimedOutException)
>
> All:
>
> I have been trying to take advantage of the InOut pattern over JMS. I am using Camel 2.4.0 and ActiveMQ 5.3.1
>
> I have created a simple example that can be run to replicate the problem I am experiencing. Attached please find the source code plus ant build file. Within the libs folder is a file listing all required jars (sorry - I wasn't sure about uploading a 30M file to this list!).
>
> Once you have the necessary jars in place under libs/compile then in two terminal windows:
>
> ant clean run-consumer
>
> ant run-publisher
>
> The consumer implements the InOut processor and the publisher invokes it over JMS.
>
> Within the second terminal window you will soon see
> [java] Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis. Exchange[Message: John]
> [java] at org.apache.camel.component.jms.JmsProducer.processInOut(JmsProducer.java:265)
> [java] at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:147)
>
> Originally I had specified 5 consumers in the metadata/test-env/res/applicationContext-consumer.xml file. However, I can set the number of consumers down to one and the same problem occurs. BTW, we use a clustered environment - so I would like to specify multiple consumers and use multiple computers.
>
> Any insight into this would be greatly appreciated!!
>
> TIA,
>
> Mike L. (aka patzerbud)
AW: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by Christian Schneider <cs...@talend.com>.
Hi,
I have no yet really run your example but I have successfully run similar examples so camel should be able to do what you want to achieve here.
Some ideas how your code can be made simpler. For the processor you should use the bean features of camel. Simply create your processor like this:
class MyProcessor {
public String doStuff(String inMsg) {
return "hello " + inMsg;
}
}
This does the same as your code.
The next thing is you do not need to use inOut jms and activemq components use InOut by default. To call the bean simply use:
<to uri="myBean"/>
and define the bean in spring:
<bean id="myBean" class="MyProcessor"/>
This should work nicely.
Christian
Von: Mike L. [mailto:patzerbud@hotmail.com]
Gesendet: Montag, 21. März 2011 20:46
An: users@camel.apache.org
Betreff: InOut over JMS always leads to Timout (ExchangeTimedOutException)
All:
I have been trying to take advantage of the InOut pattern over JMS. I am using Camel 2.4.0 and ActiveMQ 5.3.1
I have created a simple example that can be run to replicate the problem I am experiencing. Attached please find the source code plus ant build file. Within the libs folder is a file listing all required jars (sorry - I wasn't sure about uploading a 30M file to this list!).
Once you have the necessary jars in place under libs/compile then in two terminal windows:
ant clean run-consumer
ant run-publisher
The consumer implements the InOut processor and the publisher invokes it over JMS.
Within the second terminal window you will soon see
[java] Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis. Exchange[Message: John]
[java] at org.apache.camel.component.jms.JmsProducer.processInOut(JmsProducer.java:265)
[java] at org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:147)
Originally I had specified 5 consumers in the metadata/test-env/res/applicationContext-consumer.xml file. However, I can set the number of consumers down to one and the same problem occurs. BTW, we use a clustered environment - so I would like to specify multiple consumers and use multiple computers.
Any insight into this would be greatly appreciated!!
TIA,
Mike L. (aka patzerbud)
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
So, further testing has revealed that it was not my configuration file. Instead I found differences based on the version of ActiveMQ I used:
5.3.1 works fine
5.3.2 works fine
5.4.2 fails ~30% of the time
5.5.0 works fine
> To: users@camel.apache.org
> Subject: RE: InOut over JMS always leads to Timout (ExchangeTimedOutException)
> Date: Sat, 2 Apr 2011 13:47:48 -0500
>
>
> All:
>
> I just downloaded and installed ActiveMQ 5.5.0 and when I ran my test it passed!
>
> Although it could be that the new version of ActiveMQ fixed the problem - right now I suspect my activemq.xml configuration was in some way causing this. I will do more investigation and report back with my findings.
>
> Thanks to everyone who replied.
>
> Mike L. (aka patzerbud)
>
>
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
All:
I just downloaded and installed ActiveMQ 5.5.0 and when I ran my test it passed!
Although it could be that the new version of ActiveMQ fixed the problem - right now I suspect my activemq.xml configuration was in some way causing this. I will do more investigation and report back with my findings.
Thanks to everyone who replied.
Mike L. (aka patzerbud)
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
I ran a test with DEBUG logging turned on and have attached the output. As you can see below 6 out of 20 messages failed.
2011-04-02 11:12:16,998 INFO [main] (HelloPublisher.java:58) -response: hello John 1
2011-04-02 11:12:33,454 INFO [main] (HelloPublisher.java:58) -response: hello John 2
2011-04-02 11:12:53,616 INFO [main] (HelloPublisher.java:58) -response: hello John 4
2011-04-02 11:13:03,441 INFO [main] (HelloPublisher.java:58) -response: hello John 5
2011-04-02 11:13:23,670 INFO [main] (HelloPublisher.java:58) -response: hello John 7
2011-04-02 11:13:23,727 INFO [main] (HelloPublisher.java:58) -response: hello John 8
2011-04-02 11:13:33,441 INFO [main] (HelloPublisher.java:58) -response: hello John 9
2011-04-02 11:13:53,731 INFO [main] (HelloPublisher.java:58) -response: hello John 11
2011-04-02 11:14:03,441 INFO [main] (HelloPublisher.java:58) -response: hello John 12
2011-04-02 11:14:23,806 INFO [main] (HelloPublisher.java:58) -response: hello John 14
2011-04-02 11:14:33,440 INFO [main] (HelloPublisher.java:58) -response: hello John 15
2011-04-02 11:14:53,861 INFO [main] (HelloPublisher.java:58) -response: hello John 17
2011-04-02 11:15:03,441 INFO [main] (HelloPublisher.java:58) -response: hello John 18
2011-04-02 11:15:23,922 INFO [main] (HelloPublisher.java:58) -response: hello John 20
Any help would be greatly appreciated!
TIA,
Mike L. (aka patzerbud)
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
Claus:
Once again, thank you for your reply.
Even my real-world application processes the messages much, much faster than 20 seconds. However, I can also replicate the problem using the sample class below (which reads the in message, appends a String to it, and returns the result). So, as I mentioned in a previous post, I believe it shows a problem consuming messages.
Interestingly, if I modify the ActiveMQ log4j.properties file, then the error rate goes down to < 1%. Normally, the error rate is 15-30% - significantly different!
public class HelloProcessor implements Processor {
private static final Log LOG = LogFactory.getLog(HelloProcessor.class);
public void process(org.apache.camel.Exchange exchange) {
String inMsg = getInputMessage(exchange);
String outMsg = new String("hello " + inMsg);
//exchange.getIn().setBody(outMsg); // this didn't work out so well...
// change the message to say Hello
exchange.getOut().setBody(outMsg);
// copy headers from IN to OUT to propagate them
exchange.getOut().setHeaders(exchange.getIn().getHeaders());
}
String getInputMessage(org.apache.camel.Exchange exchange) {
String content = exchange.getIn().getBody(String.class);
if (content != null) return content;
return "";
}
}
If you could run the sample classes I sent in the original post you can see for yourself how often synchronous messaging over JMS using Camel times out. If it would help, I could try to "Mavenize" the project so you wouldn't have to put all the dependent jars in the project.
Thanks,
Mike L. (aka patzerbud)
>
> If the processing of the messages is very slow then you can set a
> higher value for the timeout (20 sec by default)
>
> Its the requestTimeout option
> http://camel.apache.org/jms
>
Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
Posted by Claus Ibsen <cl...@gmail.com>.
If the processing of the messages is very slow then you can set a
higher value for the timeout (20 sec by default)
Its the requestTimeout option
http://camel.apache.org/jms
On Wed, Mar 30, 2011 at 11:56 PM, Mike L. <pa...@hotmail.com> wrote:
>>> Attachment #1 (ActiveMQ_DLQ_Msg.png) shows a sample of such a message.
>
> Hopefully, the attachment stays attached this time... (or I give up)
>
>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
>> Attachment #1 (ActiveMQ_DLQ_Msg.png) shows a sample of such a message.
Hopefully, the attachment stays attached this time...
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
Paul:
Thank you for your response. Please see my comments inline below...
> To: users@camel.apache.org
> Date: Tue, 29 Mar 2011 04:35:51 -0700
> Subject: Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
>
> Mike,
>
> I can't see your original description of the problem in this thread, so
> maybe I'm regurgitating old and obvious advice, but...
I hope you can view the original description of the problem as well as the entire thread here:
http://camel.465427.n5.nabble.com/InOut-over-JMS-always-leads-to-Timout-ExchangeTimedOutException-td4237336.html
>
> Are both test classes using JMS endpoints inside a Camel route? And do
> they both have the necessary JMS/ActiveMQ configuration in Spring XML?
My original example/test Spring files did not have a route for the publisher.
I added this route:
<route>
<from uri="vm:Hello.InOut"/>
<inOut uri="activemq:Hello.InOut?exchangePattern=InOut"/>
</route>
to the publisher, but that didn't change anything. Approx. 30% of the messages timeout.
>
> Have you turned on debug logging? This should show whether your JMS
> producer is actually failing to connect, or failing to receive the
> response.
>
> If it's failing to connect, do the logs indicate what specific call
> failed? Maybe your broker is unavailable, or maybe it cannot create the
> queue in question, or maybe your JNDI server cannot resolve it; etc...
> you get the idea.
All good thoughts! I did some more testing and have narrowed down (hopefully) what is going on.
The publisher sends all messages successfully.
Approximately 30% of the messages timeout (i.e. the response is not received).
When a response is not received (in a timely fashion) then ActiveMQ removes the message from the original queue and delivers it to the DLQ. Attachment #1 (ActiveMQ_DLQ_Msg.png)
shows a sample of such a message.
I have also attached the debug log from the consumer; with the hope that it will help.
In summary, I believe the consumer is failing to consume the message. When the timeout occurs in the publisher, then he stops listening on the temp-queue and ActiveMQ then moves the original message to the DLQ. (Alternatively, the message is published with a TTL and ActiveMQ moves the original message to the DLQ after the message/TTL has expired. I'm unsure of the inner workings of AMQ.)
>
> If it's timing out while waiting for a response, then check the
> JMSReplyTo header; is your consumer actually delivering the response
> here?
>
> Regards,
> Paul
>
>
> On Mon, 2011-03-28 at 23:39 -0700, Claus Ibsen wrote:
> > Hi
> >
> > See this FAQ
> > http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
> >
> > And change your logic to set the answer on the IN thats just much
> > easier, in the HelloProcessor.
> >
> >
I tried this - it seemed to make the problem much worse.
Thank you both for your responses. Any further thoughts/advice would be greatly appreciated!
TIA,
Mike L. (aka patzerbud)
Re: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by Paul Lowry <pl...@newbay.com>.
Mike,
I can't see your original description of the problem in this thread, so
maybe I'm regurgitating old and obvious advice, but...
Are both test classes using JMS endpoints inside a Camel route? And do
they both have the necessary JMS/ActiveMQ configuration in Spring XML?
Have you turned on debug logging? This should show whether your JMS
producer is actually failing to connect, or failing to receive the
response.
If it's failing to connect, do the logs indicate what specific call
failed? Maybe your broker is unavailable, or maybe it cannot create the
queue in question, or maybe your JNDI server cannot resolve it; etc...
you get the idea.
If it's timing out while waiting for a response, then check the
JMSReplyTo header; is your consumer actually delivering the response
here?
Regards,
Paul
On Mon, 2011-03-28 at 23:39 -0700, Claus Ibsen wrote:
> Hi
>
> See this FAQ
> http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
>
> And change your logic to set the answer on the IN thats just much
> easier, in the HelloProcessor.
>
>
> On Mon, Mar 28, 2011 at 10:02 PM, Mike L. <pa...@hotmail.com>
> wrote:
> >
> > Claus:
> >
> > Thank you very much for your response. However, using the few test
> classes I wrote which illustrate the problem I have been running them
> on the same box (my local dev machine). So, the two test classes as
> well as ActiveMQ are all running locally...
> >
> > Any help would be greatly appreciated. My manager has indicated that
> if I cannot get this feature to work he is skeptical of using Camel at
> all...
> >
> > TIA,
> >
> > Mike L. (aka patzerbud)
> >
> >
> >> From: claus.ibsen@gmail.com
> >> Date: Fri, 25 Mar 2011 19:07:30 +0100
> >> Subject: Re: InOut over JMS always leads to Timout
> (ExchangeTimedOutException)
> >> To: users@camel.apache.org
> >>
> >> As always when passing messages over JMS make sure the clock is
> synced
> >> between the boxes.
> >>
> >> There is a timestamp plugin for AMQ which can help
> >> http://activemq.apache.org/timestampplugin.html
> >>
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> FuseSource
> >> Email: cibsen@fusesource.com
> >> Web: http://fusesource.com
> >> Twitter: davsclaus
> >> Blog: http://davsclaus.blogspot.com/
> >> Author of Camel in Action: http://www.manning.com/ibsen/
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
>
>
STRICTLY PRIVATE, CONFIDENTIAL AND PRIVILEGED COMMUNICATION.
This message (including attachments) may contain information that is
privileged, confidential or protected from disclosure. They are intended
solely for the use of the intended recipient. If you are not the
intended recipient, you are hereby notified that dissemination,
disclosure, copying, distribution, printing, transmission or use of this
message or any information contained in it is strictly prohibited. If
you have received this message from NewBay Software in error, please
immediately notify the sender by reply email and delete this message
from your computer. The content of this e-mail, and any files
transmitted with it, may have been changed or altered without the
consent of the author. Although we have taken steps to ensure that this
email and attachments are free from any virus, we advise that in keeping
with good computing practice the recipient should ensure they are
actually virus free.
Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
See this FAQ
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
And change your logic to set the answer on the IN thats just much
easier, in the HelloProcessor.
On Mon, Mar 28, 2011 at 10:02 PM, Mike L. <pa...@hotmail.com> wrote:
>
> Claus:
>
> Thank you very much for your response. However, using the few test classes I wrote which illustrate the problem I have been running them on the same box (my local dev machine). So, the two test classes as well as ActiveMQ are all running locally...
>
> Any help would be greatly appreciated. My manager has indicated that if I cannot get this feature to work he is skeptical of using Camel at all...
>
> TIA,
>
> Mike L. (aka patzerbud)
>
>
>> From: claus.ibsen@gmail.com
>> Date: Fri, 25 Mar 2011 19:07:30 +0100
>> Subject: Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
>> To: users@camel.apache.org
>>
>> As always when passing messages over JMS make sure the clock is synced
>> between the boxes.
>>
>> There is a timestamp plugin for AMQ which can help
>> http://activemq.apache.org/timestampplugin.html
>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
RE: InOut over JMS always leads to Timout
(ExchangeTimedOutException)
Posted by "Mike L." <pa...@hotmail.com>.
Claus:
Thank you very much for your response. However, using the few test classes I wrote which illustrate the problem I have been running them on the same box (my local dev machine). So, the two test classes as well as ActiveMQ are all running locally...
Any help would be greatly appreciated. My manager has indicated that if I cannot get this feature to work he is skeptical of using Camel at all...
TIA,
Mike L. (aka patzerbud)
> From: claus.ibsen@gmail.com
> Date: Fri, 25 Mar 2011 19:07:30 +0100
> Subject: Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
> To: users@camel.apache.org
>
> As always when passing messages over JMS make sure the clock is synced
> between the boxes.
>
> There is a timestamp plugin for AMQ which can help
> http://activemq.apache.org/timestampplugin.html
>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
Re: InOut over JMS always leads to Timout (ExchangeTimedOutException)
Posted by Claus Ibsen <cl...@gmail.com>.
As always when passing messages over JMS make sure the clock is synced
between the boxes.
There is a timestamp plugin for AMQ which can help
http://activemq.apache.org/timestampplugin.html
On Mon, Mar 21, 2011 at 8:45 PM, Mike L. <pa...@hotmail.com> wrote:
> All:
>
> I have been trying to take advantage of the InOut pattern over JMS. I am
> using Camel 2.4.0 and ActiveMQ 5.3.1
>
> I have created a simple example that can be run to replicate the problem I
> am experiencing. Attached please find the source code plus ant build file.
> Within the libs folder is a file listing all required jars (sorry - I wasn't
> sure about uploading a 30M file to this list!).
>
> Once you have the necessary jars in place under libs/compile then in two
> terminal windows:
>
> ant clean run-consumer
>
> ant run-publisher
>
> The consumer implements the InOut processor and the publisher invokes it
> over JMS.
>
> Within the second terminal window you will soon see
> [java] Caused by: org.apache.camel.ExchangeTimedOutException: The OUT
> message was not received within: 20000 millis. Exchange[Message: John]
> [java] at
> org.apache.camel.component.jms.JmsProducer.processInOut(JmsProducer.java:265)
> [java] at
> org.apache.camel.component.jms.JmsProducer.process(JmsProducer.java:147)
>
> Originally I had specified 5 consumers in the
> metadata/test-env/res/applicationContext-consumer.xml file. However, I can
> set the number of consumers down to one and the same problem occurs. BTW, we
> use a clustered environment - so I would like to specify multiple consumers
> and use multiple computers.
>
> Any insight into this would be greatly appreciated!!
>
> TIA,
>
> Mike L. (aka patzerbud)
>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/