We recently upgraded to CXF 2.1.3 from 2.1.2. After the upgrade we noticed that JMS conduits with a reply to queue were not always working if we had multiple instances running. I didn't dive into the problem real deep, but rather just removed the reply to queue config so that it would use a temporary queue. That fixed the problem.
It looks like to me that the new implemenation of the JMS conduit is broken if you have multiple instances of a conduit running against the same reply to queue. It's possible that this could be fixed with the new Spring configuration, but it is not backwards compatible with 2.1.2. I'm posting this to list first to see if anyone else has seen this. Let me know if you would like me to open a defect. -- View this message in context: http://www.nabble.com/CXF-2.1.3-JMS-Conduit-tp20447067p20447067.html Sent from the cxf-user mailing list archive at Nabble.com.
