Using JMS BC with ActiveMQ

You can configure the JMS BC to connect to an ActiveMQ broker via its built-in, client-side JNDI support. This makes it possible to configure a connection to an external broker or to start an embedded broker for transient messaging on a specified port. For each of these methods, it is advised that you add activemq-all-x.x.x.jar to your domain's classpath (e.g. by dropping it into glassfish\domains\domain1\lib\ext).

Connecting to an external ActiveMQ broker (non-XA)

NB: This only applies for .

One or more destination-neutral connection factories (non-XA) can be declared in the JNDI settings of the JMSJCA options to be read when the InitialContext is created. XA interfaces need to be bound to a JNDI server manually to be used with OpenESB.

Sample WSDL:

     <service name="JMSOutService">
        <port name="Write_OutPort" binding="tns:JMSOutBinding">
            <jms:address connectionURL="jndi://" username="admin" password="admin">
                <jms:jmsjcaOptions><![CDATA[#For JNDI (ConnectionURL=jndi://)
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
connectionFactoryNames=ConnectionFactory,QueueConnectionFactory,TopicConnectionFactory
JMSJCA.UnifiedCF=ConnectionFactory
JMSJCA.TopicCF=TopicConnectionFactory 
JMSJCA.QueueCF=QueueConnectionFactory
java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory
java.naming.provider.url=tcp://localhost:61616
#java.naming.provider.url=vm:broker:(tcp://localhost:61617)
]]></jms:jmsjcaOptions>
            </jms:address>
        </port>
    </service>

Starting and connecting to an internal ActiveMQ broker (non-XA)

As above, but set:

java.naming.provider.url=vm://myEmbeddedBroker?create=true&waitForStart=5000

This URL ensures that the first connection created will start the broker (connect=true is the default) and provides a 5 second delay before the connection is formed for the broker to start. More options can be found here.