Ansvering my own question in part: The consumer is created with a selector that looks like this:
"JMSCorrelationID LIKE '2dae737a337048cda147e911e958cddb%'" Using a correlationIdPrefix (not the message correlation id). Which means it may match multiple messages ideed... This also explains why they will remain active (i.e. one per JMSConduit). -- View this message in context: http://cxf.547215.n5.nabble.com/SOAP-over-JMS-Lifecycle-of-response-queue-consumer-tp5765203p5765257.html Sent from the cxf-user mailing list archive at Nabble.com.
