I resolved this issue. It turned out that when using the InOut exchange pattern with JMS, the message expiration time is set. With InOnly it is not set. It happened that my two test machines did not have clocks that were in sync, so the messages were being treated as expired with InOut, but not with InOnly.
-- View this message in context: http://camel.465427.n5.nabble.com/InOut-message-over-JMS-across-firewall-tp3408704p3408906.html Sent from the Camel - Users mailing list archive at Nabble.com.
