Home/ Questions/Q 8397983
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T20:55:10+00:00

In my test I run inmem ActiveMQ and then instantiate ActiveMQConnectionFactory and do whatever

  • 0

In my test I run inmem ActiveMQ and then instantiate ActiveMQConnectionFactory and do whatever I want in order to test it. I used this because that seemed to be the easiest way to create integration test. I thought the switch from ActiveMQConnectionFactory to com.ibm.mq.jms.MQTopicConnectionFactory would be straightforward. But it apparently is not. What would be the mapping from this snippet

<bean id="activeMqConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
        <constructor-arg value="vm://localhost:61616"/>
</bean>

to that one:

<bean id="ibmConnectionFactory" class="com.ibm.mq.jms.MQTopicConnectionFactory">
    <property name="hostName" value="??"/>
    <property name="port" value="??"/>
    <property name="queueManager" value="??"/>
    <property name="channel" value="??"/>
    <property name="transportType" value="?"/>
</bean>

Would that be even possible without some kind of weird bridges Camel has?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is not possible. The JMS specification covers the API and behavior but vendors are free to implement any wire format and communication protocols that they wish. WebSphere MQ uses it’s own formats and protocols and Active MQ has its own formats and protocols.

    Bridge applications function by reading messages into memory from one transport then writing that message to the other transport. Although this works at a basic level, the two transports have different destination namespaces and security realms so these interfaces tend to be hard-coded point-to-point routes. This is usually the best you can expect when mixing JMS transport providers.

    • 0