Oracle GlassFish Message Queue 4.4.2 Developer's Guide for Java Clients

ProcedureTo Consume Messages

  1. Get a connection factory.

    A Message Queue ConnectionFactory object encapsulates all of the needed configuration properties for creating connections to the Message Queue message service. You can obtain such an object either by direct instantiation

    ConnectionFactory  myFctry = new com.sun.messaging.ConnectionFactory();

    or by looking up a predefined connection factory using the Java Naming and Directory Interface (JNDI). In the latter case, all of the connection factory’s properties will have been preconfigured to the appropriate values by your Message Queue administrator. If you instantiate the factory object yourself, you may need to configure some of its properties explicitly: for instance,

                       "localhost:7676, broker2:5000, broker3:9999");

    See Obtaining a Connection Factory for further discussion.

  2. Create a connection.

    A Connection object is an active connection to the Message Queue message service, created by the connection factory you obtained in Developing a Client Application:

    Connection  myConnection = myFactory.createConnection();

    See Using Connections for further discussion.

  3. Create a session for communicating with the message service.

    A Session object represents a single-threaded context for producing and consuming messages. Every session exists within the context of a particular connection and is created by that connection’s createSession method:

    Session  mySession = myConnection.createSession(false,

    The first (boolean) argument specifies whether the session is transacted. The second argument is the acknowledgment mode, such as AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, or DUPS_OK_ACKNOWLEDGE; these are defined as static constants in the JMS Session interface. See Acknowledgment Modes and Transacted Sessions for further discussion.

  4. Get a destination from which to receive messages.

    A Destination object encapsulates provider-specific naming syntax and behavior for a message destination, which may be either a point-to-point queue or a publish/subscribe topic (see Messaging Domains). You can obtain such an object by direct instantiation

    Destination  myDest = new com.sun.messaging.Queue("myDest");

    or by looking up a predefined destination using the JNDI API. See Working With Destinations for further discussion.

  5. Create a message consumer for receiving messages from this destination.

    A MessageConsumer object is created by a session and associated with a particular destination:

    MessageConsumer  myConsumer = mySession.createConsumer(myDest);

    See Receiving Messages for further discussion.

  6. Start the connection.

    In order for a connection’s message consumers to begin receiving messages, you must start the connection by calling its start method:


    See Using Connections for further discussion.

  7. Receive a message.

    The message consumer’s receive method requests a message from the destination with which the consumer is associated:

    Message  inMsg = myConsumer.receive();

    This method is used for synchronous consumption of messages. You can also configure a message consumer to consume messages asynchronously, by creating a message listener and associating it with the consumer. See Receiving Messages for further discussion.

  8. Retrieve the message’s content and properties.

    Each type of message has its own methods for extracting the contents of the message body. For instance, you can retrieve the content of a text message with the statements

    TextMessage  txtMsg  = (TextMessage) inMsg;
    String       msgText = txtMsg.getText();

    In addition, you may need to retrieve some of the message’s header fields: for instance,

    msgPriority = inMsg.getJMSPriority();

    You can also use message methods to retrieve custom message properties of your own: for instance,

    magicWord = inMsg.getStringProperty("MagicWord");

    See Processing Messages for further discussion.

  9. Close the session.

    When there are no more messages to consume, you should close the session


    allowing Message Queue to free any resources it may have associated with the session. See Working With Sessions for further discussion.

  10. Close the connection.

    When all sessions associated with a connection have been closed, you should close the connection by calling its close method:


    See Using Connections for further discussion.