Thank you Pontus and Willem for the recommendations. We are using JBoss 4.0.4 and 5.1.0 and rather topics than queues and we have several source systems (even our Jboss servers can do that) using several protocols to provide messages for that topic.
Could be possible that we go for 7.1.1 for both but this is not yet decided (due to HornetQ this would be an option). Also the message exchange is only needed when both products (i.e. servers) are installed. The bridge between our servers , which I've already tried out, works quite fine, but there are some ugly side effects like having tons of errors in case of problems.=20 As you can imagine, the customers don't want to analyze log files to find out if connection is ok or not. Giving access to the JMX console is also not an option.=20 Beside of these things the JMS persistence on these "old" JBoss versions is RDBMS based, which means also that huge DB maintenance is required. As you all know, the customer just want to see a green or red "traffic light" and eventually the reason to be able to react. I thought, maybe this kind of functionality is much easier to be realized with Camel (including own local Db) than using that bridge. I've checked again the possibilities in Camel and it looks like the MongoDb would also be an option to persist the messages locally. I have to take a closer look to that because first steps went wrong ;-) Thank you again. -- View this message in context: http://camel.465427.n5.nabble.com/How-to-keep-sending-in-chronological-order-even-when-peer-was-down-for-a-while-tp5716501p5716542.html Sent from the Camel - Users mailing list archive at Nabble.com.
