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. <patzer...@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.ib...@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: cib...@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: cib...@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.
