This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • JNDI Support
Skip to end of metadata
Go to start of metadata

ActiveMQ will work with any JNDI provider capable of storing Java objects. However it is common to require a JNDI initial context to be able to run many JMS example programs, like Sun's JMS tutorial.

So we provide a simple JNDI InitialContextFactory which can be used to lookup JMS connection factory objects as well as Destination objects. For example if you place this file on your classpath, you can look inside the InitialContext and lookup ConnectionFactory objects and Destinations etc.

You can edit the file to configure the ActiveMQConnectionFactory's properties such as brokerURL and whether or not there should be an embedded broker etc. See how to embed a broker in a connection for more details.

ActiveMQ JNDI Tutorial

This is a quick one page tutorial on how to setup and use JNDI to create a connection to ActiveMQ. The first thing is ActiveMQ does not provide a full JNDI server. This means JMS clients need to use properties files to create a JNDI IntialContextFactory. If you need an example properties file, you can look the source distribution Before we proceed, here are the properties.









Make sure to add activemq-<version>.jar and spring-1.x.jar to your classpath. If the libraries are not in the classpath, you will get a ClassNotFoundException at runtime. If you get ClassNotFoundException, try printing out the classpath and check it is present. You can also run ActiveMQ with -verbose option to verify the jar was loaded correctly.

Sample Code


Notice the name of the topic in the sample is MyTopic. ActiveMQ will read the files and creates the topics and queues in a lazy fashion. The prefix topic and queue is stripped, so the JNDI name begins after the prefix.

Once you have the edited and ready, it needs to be accessible to your application. The easiest way is to add to a jar file. When new InitialContext() is called, it will scan the resources and find the file. If you get javax.naming.NamingException, it usually means the file is not accessible.

You can also try to create a new initial context using either an instance of properties file or a map. For example, the approach recommended by JMS specification will work just fine.

Example Recommended by Specification


If ActiveMQ is embedded within an EJB container, you will need to look at the containers documentation for the correct JNDI values.

Dynamically Creating Destinations

For the easiest possible configuration with JNDI based programs, there are two dynamic contexts, namely:

  • dynamicQueues
  • dynamicTopics

These allow you to lookup queues and topics using JNDI without any configuration.

For example, if you use the following name to lookup into JNDI:

you will get back an ActiveMQQueue of the name FOO.BAR. This can be very handy if you can easily reconfigure the JNDI name to use to lookup something in JNDI, but don't want to have to double configure a to match.

Working With Embedded Brokers

It is often useful to use an embedded broker in the same JVM as the JMS client. For this see How do I embed a Broker inside a Connection.

If you want to use an embedded broker with your JNDI provider you can just use the VM Transport to connect to the broker in your URL. e.g. to create a purely in JVM broker use this URI

If you want to customize the broker use something like this:

More options are available in the VM Transport Reference

Example Java Code

Once you have configured JNDI on the classpath you can run any normal JMS application such as the following example. Notice that the Java code just uses pure JMS APIs and is not in any way ActiveMQ specific

java 2)) {"Usage: java SimpleProducer []"); System.exit(1); }  destinationName = args[0];"Destination name is " + destinationName); if (args.length == 2) { numMsgs = (new Integer(args[1])).intValue(); } else { numMsgs = 1; } /* * Create a JNDI API InitialContext object */ try { jndiContext = new InitialContext(); } catch (NamingException e) {"Could not create JNDI API context: " + e.toString()); System.exit(1); }  /* * Look up connection factory and destination. */ try { connectionFactory = (ConnectionFactory)jndiContext.lookup("ConnectionFactory"); destination = (Destination)jndiContext.lookup(destinationName); } catch (NamingException e) {"JNDI API lookup failed: " + e); System.exit(1); }  /* * Create connection. Create session from connection; false means * session is not transacted. Create sender and text message. Send * messages, varying text slightly. Send end-of-messages message. * Finally, close the connection. */ try { connection = connectionFactory.createConnection(); session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); producer = session.createProducer(destination); TextMessage message = session.createTextMessage();  for (int i = 0; i < numMsgs; i++) { message.setText("This is message " + (i + 1));"Sending message: " + message.getText()); producer.send(message); }  /* * Send a non-text control message indicating end of messages. */ producer.send(session.createMessage()); } catch (JMSException e) {"Exception occurred: " + e); } finally { if (connection != null) { try { connection.close(); } catch (JMSException ignored) {} } } } } ]]>
  • No labels

1 Comment

  1. - Couple of broken links.

    -  org.activemq.jndi.ActiveMQInitialContextFactory should be org.apache.activemq.jndi.ActiveMQInitialContextFactory

    - Couple of references to out-dated jars, activemq-1.1.jar and spring-1.1.jar.

    - Couple of references to out-dated resources: activemq-1.1/src/test/