-
Bug
-
Resolution: Done
-
Major
-
7.4.12.GA
Summary: Migrating JMS Bridge from 6.4 environment to 7.4 will always fails given its absence of module.
Reproduction: Bellow cannot be migrated without module="org.apache.activemq.artemis"; upon addition of that, it works.
<jms-bridge name="fbtilot-monitorQueue-bridge">
<source>
<connection-factory name="/ConnectionFactory"/>
<destination name="/queue/MonitorQueue"/>
</source>
<target>
<connection-factory name="/jms/RemoteConnectionFactory"/>
<destination name="/queue/MonitorQueue"/>
<user>bridge</user>
<password>jmsbr!dge1</password>
<context>
<property key="java.naming.factory.initial" value="org.jboss.naming.remote.client.InitialContextFactory"/>
<property key="java.naming.provider.url" value="remote://192.168.1.1:4447,remote://192.168.1.2:4447"/>
<property key="java.naming.security.principal" value="bridge"/>
<property key="java.naming.security.credentials" value="jmsbr!dge1"/>
</context>
</target>
<quality-of-service>AT_MOST_ONCE</quality-of-service>
<failure-retry-interval>10000</failure-retry-interval>
<max-retries>-1</max-retries>
<max-batch-size>500</max-batch-size>
<max-batch-time>500</max-batch-time>
<add-messageID-in-header>true</add-messageID-in-header>
</jms-bridge>
Workaround: Adding manually module="org.apache.activemq.artemis" on the configuration the migration works.