PAX JMS forces JMS 2.0 and doesn't work property with ActiveMQ

Description

Using a connection factory created by Pax JMS, we systematically have:

I'm fixing to cleanly support ActiveMQ in pax-jms-activemq.

Environment

None

Activity

Show:
Jean-Baptiste Onofre
May 22, 2018, 12:25 PM

The workaround is to use transx for pooling. It's possible to define this using:

in the org.ops4j.connectionfactory.UUID.

I've updated Karaf JMS service accordingly.

Jean-Baptiste Onofre
May 22, 2018, 12:25 PM

By the way, it needs additional features to be installed: pax-jms-transx-pool, pax-jms-activemq.

Assignee

Jean-Baptiste Onofre

Reporter

Jean-Baptiste Onofre

Labels

None

Components

Affects versions

Priority

Blocker
Configure