The following program shows how to send and receive a message using the Apache Qpid JMS client for AMQP 0-10 . JMS programs typically use JNDI to obtain connection factory and destination objects which the application needs. In this way the configuration is kept separate from the application code itself.
In this example, we create a JNDI context using a properties file, use the context to lookup a connection factory, create and start a connection, create a session, and lookup a destination from the JNDI context. Then we create a producer and a consumer, send a message with the producer and receive it with the consumer. This code should be straightforward for anyone familiar with JMS.
Example 1.1. "Hello world!" in Java
package org.apache.qpid.example.jmsexample.hello; import javax.jms.*; import javax.naming.Context; import javax.naming.InitialContext; import java.util.Properties; public class Hello { public Hello() { } public static void main(String[] args) { Hello producer = new Hello(); producer.runTest(); } private void runTest() { try { Properties properties = new Properties(); properties.load(this.getClass().getResourceAsStream("hello.properties")); Context context = new InitialContext(properties); ConnectionFactory connectionFactory = (ConnectionFactory) context.lookup("qpidConnectionfactory"); Connection connection = connectionFactory.createConnection(); connection.start(); Session session=connection.createSession(false,Session.AUTO_ACKNOWLEDGE); Destination destination = (Destination) context.lookup("topicExchange"); MessageProducer messageProducer = session.createProducer(destination); MessageConsumer messageConsumer = session.createConsumer(destination); TextMessage message = session.createTextMessage("Hello world!"); messageProducer.send(message); message = (TextMessage)messageConsumer.receive(); System.out.println(message.getText()); connection.close(); context.close(); } catch (Exception exp) { exp.printStackTrace(); } } }
Loads the JNDI properties file, which specifies connection properties, queues, topics, and addressing options. See below for further details. | |
Creates the JNDI initial context. | |
Creates a JMS connection factory for Qpid. | |
Creates a JMS connection. | |
Activates the connection. | |
Creates a session. This session is not transactional (transactions='false'), and messages are automatically acknowledged. | |
Creates a destination for the topic exchange, so senders and receivers can use it. | |
Creates a producer that sends messages to the topic exchange. | |
Creates a consumer that reads messages from the topic exchange. | |
Reads the next available message. | |
Closes the connection, all sessions managed by the connection, and all senders and receivers managed by each session. | |
Closes the JNDI context. |
The contents of the hello.properties file are shown below.
Example 1.2. JNDI Properties File for "Hello world!" example
java.naming.factory.initial = org.apache.qpid.jndi.PropertiesFileInitialContextFactory # connectionfactory.[jndiname] = [ConnectionURL] connectionfactory.qpidConnectionfactory = amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672' # destination.[jndiname] = [address_string] destination.topicExchange = amq.topic
Defines a connection factory from which connections can be created. The syntax of a ConnectionURL is given in Section 2.2, “JNDI Properties”. | |
Defines a destination for which MessageProducers and/or MessageConsumers can be created to send and receive messages. The value for the destination in the properties file is an address string as described in Section 2.4, “Addresses”. In the JMS implementation MessageProducers are analogous to senders in the Qpid Message API, and MessageConsumers are analogous to receivers. |
Apache Qpid, Messaging built on AMQP; Copyright © 2015 The Apache Software Foundation; Licensed under the Apache License, Version 2.0; Apache Qpid, Qpid, Qpid Proton, Proton, Apache, the Apache feather logo, and the Apache Qpid project logo are trademarks of The Apache Software Foundation; All other marks mentioned may be trademarks or registered trademarks of their respective owners