Artemis' JNDI implementation is client-side only which means that JMS connection factories are configured in jndi.properties or programmatically in the environment of the appropriate initial context. Therefore you won't find connection factory configuration details in broker.xml.
I'm a bit confused by the use-case here. You mentioned that you're sending a message from your "interceptor module". Can you clarify what exactly this is? Is it an Artemis remoting interceptor? If so, you should use the core API here rather than JMS as it would be much simpler. Justin ----- Original Message ----- From: "aries.aries" <[email protected]> To: [email protected] Sent: Monday, August 22, 2016 11:09:25 AM Subject: Re: Using JMS in ActiveMQ Artemis Below is the entire content of Broker.xml <?xml version='1.0'?> <configuration xmlns="urn:activemq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd"> <jms xmlns="urn:activemq:jms"> <queue name="exampleQueue"> <durable>true</durable> </queue> </jms> <core xmlns="urn:activemq:core"> <name>master</name> <persistence-enabled>true</persistence-enabled> <journal-type>NIO</journal-type> <paging-directory>./data/paging</paging-directory> <bindings-directory>./data/bindings</bindings-directory> <journal-directory>./data/journal</journal-directory> <large-messages-directory>./data/large-messages</large-messages-directory> <journal-min-files>2</journal-min-files> <journal-pool-files>-1</journal-pool-files> <journal-buffer-timeout>68000</journal-buffer-timeout> <remoting-incoming-interceptors> <class-name>org.apache.activemq.artemis.core.protocol.mqtt.SamplingBrokerInterceptor</class-name> </remoting-incoming-interceptors> <ha-policy> <replication> <master> <check-for-live-server>true</check-for-live-server> </master> </replication> </ha-policy> <connectors> <connector name="netty-connector">tcp://172.24.25.123:61616</connector> </connectors> <acceptors> <acceptor name="netty-acceptor">tcp://172.24.25.123:61616</acceptor> </acceptors> <broadcast-groups> <broadcast-group name="bg-group1"> <group-address>${udp-address:231.7.7.7}</group-address> <group-port>9876</group-port> <broadcast-period>1000</broadcast-period> <connector-ref>netty-connector</connector-ref> </broadcast-group> </broadcast-groups> <discovery-groups> <discovery-group name="dg-group1"> <group-address>${udp-address:231.7.7.7}</group-address> <group-port>9876</group-port> <refresh-timeout>5000</refresh-timeout> </discovery-group> </discovery-groups> <cluster-connections> <cluster-connection name="my-cluster"> <address>jms</address> <connector-ref>netty-connector</connector-ref> <discovery-group-ref discovery-group-name="dg-group1"/> </cluster-connection> </cluster-connections> <security-settings> <security-setting match="#"> <permission type="createNonDurableQueue" roles="a"/> <permission type="deleteNonDurableQueue" roles="a"/> <permission type="createDurableQueue" roles="a"/> <permission type="deleteDurableQueue" roles="a"/> <permission type="consume" roles="a"/> <permission type="browse" roles="a"/> <permission type="send" roles="a"/> <permission type="manage" roles="a"/> </security-setting> </security-settings> </core> </configuration> -- View this message in context: http://activemq.2283324.n4.nabble.com/Using-JMS-in-ActiveMQ-Artemis-tp4715693p4715709.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
