This means you will need to choose a different pooling solution. Maybe Tibco already delivers one. We can also ask the ActiveMQ team if the pooling support can be decoupled from ActiveMQ.
Christian 2016-01-28 9:22 GMT+01:00 BjornA <[email protected]>: > BjornA wrote > > I was under the impression that PoolingConnectionFactory > > (PooledConnectionFactory?) is tightly coupled to active mq (I'm using > > tibco) but I will give that a shot as well. > > Just a quick update on my test, indeed the > "org.apache.activemq.pool.PooledConnectionFactory" requires the underlying > connection to be of active mq: > > com.tibco.tibjms.TibjmsQueueConnection cannot be cast to > org.apache.activemq.ActiveMQConnection > > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/SOAP-over-JMS-Lifecycle-of-response-queue-consumer-tp5765203p5765286.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>
