Hi Arnaud
On Sat, Jan 30, 2010 at 5:59 AM, altoro <arnaudle...@hotmail.com> wrote: > > Hi Claus, > > You're right! I should have given more details... And also right about the > fact > I should have posted this on the activemq forum since the problem was > actually > related to the activemq broker. Sorry about that! > It's okay. Just that we want to get those facts before we start dig into it. Often we know that problem X is resolved in version Y etc. > After invetigation I found out what the problem was: > The server A (see the first post) is running on a debian machine. The server > B is running > on an Ubuntu machine. I'm using camel-jms and the camel-activemq component > to implement > the JMS communication between server A and B. > After turning the activemq logs on the server B, I found out the message was > set as expired by > the broker as soon as it arrives there. And the reason was that the time on > the server A was not > correct and one day earlier than the server B (stupid mistake!). > After setting the correct time on the server A, everything works fine again. > The strange thing is that if I put the broker on a server C running on a > Windows 7, there was no problem even with the time difference. Anyway, this > message should be on > the activemq user forum and not on the Camel one so I stop talking about > it... And sorry again for the > wrong post. > Glad you got it resolved and posted back a description how to resolve it. Yeah having a network of brokers requires that the server times is in sync. Well in fact all your servers should be in sync with the time :) > Arnaud. > > > Claus Ibsen-2 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. >>> >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> >> > > -- > View this message in context: > http://old.nabble.com/JMS-InOut-issue-tp27372665p27381433.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
