Home > Articles > Programming > Java

  • Print
  • + Share This
This chapter is from the book

Sample JMS Queue Producer/Consumer

This section demonstrates simple JMS PTP and pub/sub message producers and consumers.

Configuring JMS

First, create a folder to use as a JMS file store in the file system. Create a folder called jms_store at the root level of your WebLogic Server installation.

Then, configure the JMS file store using the WebLogic Server Administration Console. Figure 7–1 shows a JMS store named "MyJMSFileStore" that is mapped to the directory \jms_store.

Figure 7–1 Creating the JMS Store

Creating the JMS Server

Next, the WebLogic Server administrator configures a JMS Server with the Administration Console. All JMS-administered objects such as destinations or connection factories exist within a JMS Server. Each WebLogic Server instance can include multiple JMS Server instances. Because these examples use persistent messages, the server administrator has specified a backing store, the file-based storage previously created (see Figure 7–2).

Figure 7–2 Creating the JMS Server

The server administrator can also create JMS connection factories at this time. Because these examples do not require any special configuration parameters, we can use the standard connection factories.

Administrator Creates JMS Destinations

After configuring the JMS Server, the server administrator creates the JMS destinations. These examples require a JMS queue named MessageQueue and a JMS topic named MessageTopic (see Figure 7–3).

Figure 7–3 Creating a JMS Queue

Sample JMS Queue Producer/Consumer

This example demonstrates a message producer, a synchronous message consumer, and an asynchronous message consumer for a JMS queue.

Message Producer

The message producer begins by creating a JNDI InitialContext and looking up the JMS QueueConnectionFactory. Because our examples use the standard JMS connection factories, it looks up "weblogic.jms.ConnectionFactory".

Context ctx = getInitialContext();
QueueConnectionFactory qConFactory =
   (QueueConnectionFactory)
   ctx.lookup("weblogic.jms.ConnectionFactory");

Now the MessageProducer looks up the JMS destination in JNDI. The server administrator created the JMS queue with the JNDI name "MessageQueue". The WebLogic Server binds the queue into the JNDI tree, making it available to clients.

Queue messageQueue = (Queue) ctx.lookup("MessageQueue");

The message producer now creates the QueueConnection and a QueueSession. The parameters to the createQueueSession call specify that it is nontransacted and uses automatic message acknowledgment. Using transactions with JMS and message acknowledgment are covered later in this chapter.

QueueConnection qCon = qConFactory.createQueueConnection();

 QueueSession session = qCon.createQueueSession(
   false, /* not a transacted session */
   Session.AUTO_ACKNOWLEDGE 
  );

Finally, the message producer creates a sender and a JMS message. This message is a TextMessage and will include only a string.

sender = session.createSender(messageQueue);

msg = session.createTextMessage();

The message producer is now prepared to send messages. The TextMessage's setText method attaches our Hello string to the message. The QueueSender's send method sends our message to the persistent queue. When the send call returns, the message producer may send another message.

msg.setText("Hello");
sender.send(msg);

Synchronous Message Consumer

The message consumer begins with an initialization code that is nearly identical to the message producer. The QueueConnectionFactory and queue are found in JNDI. Next, a QueueConnection and QueueSession are created.

Context ctx = getInitialContext();

  QueueConnectionFactory qConFactory = (QueueConnectionFactory)
   ctx.lookup("weblogic.jms.ConnectionFactory"); 

  Queue messageQueue = (Queue) ctx.lookup("MessageQueue");

  QueueConnection qCon = qConFactory.createQueueConnection();

  QueueSession session = qCon.createQueueSession(
   false, /* not a transacted session */
   Session.AUTO_ACKNOWLEDGE 
  );

The message consumer next creates a QueueReceiver from the QueueSession. Finally, the start method is called on the QueueConnection. Message delivery is inhibited until the start method is invoked. This allows a message consumer to finish initialization before messages become available.

receiver = session.createReceiver(messageQueue);

qCon.start();

A synchronous message consumer uses the receive() method to ask JMS for the next message on this destination. The receive method blocks until a message is available on this destination. This client then uses the TextMessage's getText method to retrieve the message string and prints it to the screen.

msg = (TextMessage) receiver.receive();

System.err.println("Received: "+msg.getText());

Asynchronous Message Consumer

The asynchronous message consumer begins with the same set of initialization code as a synchronous message consumer.

Context ctx = getInitialContext();

  QueueConnectionFactory qConFactory = (QueueConnectionFactory)
   ctx.lookup("weblogic.jms.ConnectionFactory"); 

  Queue messageQueue = (Queue) ctx.lookup("MessageQueue");

  QueueConnection qCon = qConFactory.createQueueConnection();

  QueueSession session = qCon.createQueueSession(
   false, /* not a transacted session */
   Session.AUTO_ACKNOWLEDGE 
  );

  receiver = session.createReceiver(messageQueue);

An asynchronous message consumer must use the receiver's setMessageListener method and pass an object that implements the javax.jms.MessageListener interface. Finally, the QueueConnection's start method begins message delivery.

receiver.setMessageListener(this);

qCon.start();

Because this is an asynchronous consumer, the JMS implementation delivers messages by calling the onMessage method. This simple implementation just prints out the message's text and returns.

public void onMessage(Message m) {
  TextMessage msg = (TextMessage) m;

  System.err.println("Received: "+msg.getText());
}

Because message delivery is asynchronous, the client program is not blocked, waiting for messages to arrive. And, because our simple example program has no other work to perform, it exits before the messages can be delivered. To prevent this, we introduce an artificial wait to ensure that the program does not exit before the producer's messages are delivered.

Running the Queue Example

This example resides in the examples/ch7/queue directory on the accompanying CD-ROM. You can run the example from that directory.

Figure 7–4 Listing of the Queue Examples Directory

Before running the queue example, the WebLogic Server's JMS implementation must be configured. This example requires a JMS Server to be created with the Administration Console. Next, a JMS queue with the JNDI name of "MessageQueue" must be created. See the preceding examples or the WebLogic Server documentation for more information on creating and configuring JMS Servers.

The example can be built with the supplied build.cmd script for Windows NT or Windows 2000. UNIX users will need to modify the script to fit their environment. There also are runProducer.cmd, runSyncConsumer.cmd, and runAsyncConsumer.cmd scripts to run the message producer, synchronous consumer, and asynchronous consumer examples.

Open a command window and execute the runProducer.cmd script.

Figure 7–5 Running the runProducer Script

In another command window, run the runAsyncConsumer script. You can see in Figure 7–6 that the messages were received successfully.

Figure 7–6 Results of Running the runAsyncConsumer Script

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020