Hi Björn, yes. As far as possible cxf will try to leave the consumer open as the overhead of creating a consumer can affect performance. It depends a bit on how you setup your reply scheme if this is possible.
I am not sure about the CachingConnectionFactory though. In the old JMS code (pre CXF 3) this was necessary but in the new code a PoolingConnectionFactory should be better. Maybe it works with a Caching one too but I never tested that case. Christian 2016-01-27 15:51 GMT+01:00 BjornA <[email protected]>: > 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. > -- -- Christian Schneider http://www.liquid-reality.de <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.liquid-reality.de> Open Source Architect http://www.talend.com <https://owa.talend.com/owa/redir.aspx?C=3aa4083e0c744ae1ba52bd062c5a7e46&URL=http%3a%2f%2fwww.talend.com>
