Please show your route and spring configure snippet, those will help us
to dig the issue.
Willem
Claus Ibsen wrote:
Hi
Get in touch with the JMS broker vendor and if you have support or
consultancy contract then use that to get access to people who can
help.
BTW when writing about a problem then you cant expect people to help
if you dont provide more details about the products used, os, versions
etc.
On Fri, Jan 29, 2010 at 3:23 PM, altoro <arnaudle...@hotmail.com> wrote:
Hi all,
I'm having a problem with an application that was working fine and for some
reason, after the reboot of the server, stopped working... This application
is on one server that communicates with another server using Camel JMS.
I have a server A from which I am sending message on a queue on server B.
The broker is embedded on server B using spring. My routes are defined using
DSL...
If I'm sending the message with an Exchange.InOnly I have no problem: The
message is read on the queue by server B. When I'm sending it with an
Exchange.InOut, the message never gets to the server B, (I know that because
the log that follows the queue EndPoint is never displayed) and of course I
get a time out exception on the server A since no response is received.
The same code was working before and if I put it on a server C, both InOnly
and InOut exchange patterns work fine. As I know by checking the logs, the
message seems never to reach the targeted server when using InOut. (So the
problem is NOT that no message is set to be sent back as out message on
server B).
I'm just wondering why... ? And also I can send a message from the server B
to the server A. That means the servers can reach each other. I'm running
out of idea! Please, if any one has an idea, I will really appreciate any
help because I'm really stuck here...
Thanks in advance.
Arnaud.
--
View this message in context:
http://old.nabble.com/JMS-InOut-issue-tp27372665p27372665.html
Sent from the Camel - Users mailing list archive at Nabble.com.
