IBM Support

Exploiting the Automatic Client Reconnect feature in WebSphere MQ JMS 7 and later

White Papers


Abstract

The objective of this technical document is to describe in detail how to exploit the automatic client reconnect feature introduced in WebSphere MQ JMS 7.0.1.
The scope is for stand alone JMS applications and not for JMS applications that run inside an application server.

Content

There are 2 scenarios covered in detail:

1) Using a sample that utilizes the Java™ Naming and Directory Interface (JNDI) which reference Connection Factories and Destinations.

2) Using a sample that does not use JNDI, and instead, specifies the characteristics of the Connection Factories and Destinations inside the code.

It is highly recommended that you review the details described in the following technote:
Technote: 1508357
Using WebSphere MQ automatic client reconnection with the WebSphere MQ classes for JMS

++ Contents

UNIX
Chapter 1: Configuration in UNIX via JMSAdmin
Chapter 2: Scenario using JNDI - UNIX
Chapter 3: Scenario NOT using JNDI - UNIX

Windows
Chapter 4: Configuration in Windows via JMSAdmin and MQ Explorer
Chapter 5: Scenario using JNDI - Windows
Chapter 6: Scenario NOT using JNDI - Windows

+++ Software used +++

Windows:
WebSphere MQ 7.0.1.6 queue manager and JMS client
Java 1.6 SR 7

Linux x86 32-bit
WebSphere MQ 7.0.1.6 queue manager and JMS client
Java 1.6 SR 9

+++ About the Samples

There are 3 samples provided with this techdoc.
JmsJndiProducerLoop.java => Uses JmsConnectionFactory and JNDI
JmsProducerLoop.java = > Uses JmsConnectionFactory (no JNDI)
JmsProducerLoopMQCF.java => Uses MQConnectionFactory (no JNDI)

They are based on the JmsJndiProducer.java and JmsProducer.java samples provided with MQ V7:
Windows: C:\Program Files\IBM\WebSphere MQ\tools\jms\samples\
UNIX: /opt/mqm/samp/jms/samples/

DISCLAIMER
All source code and/or binaries attached to this document are referred to here as "the Program". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an "AS IS" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Attached file: MQ_701_Automatic_Client_Reconnect_JMS.pdf

PDF File: MQ_701_Automatic_Client_Reconnect_JMS.pdf
Size: 700 KB
MQ_701_Automatic_Client_Reconnect_JMS.pdfMQ_701_Automatic_Client_Reconnect_JMS.pdf

Sample File: JmsJndiProducerLoop.java
JmsJndiProducerLoop.javaJmsJndiProducerLoop.java

Sample File: JmsProducerLoop.java
JmsProducerLoop.javaJmsProducerLoop.java

Sample File: JmsProducerLoopMQCF.java
JmsProducerLoopMQCF.javaJmsProducerLoopMQCF.java

[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Java","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.0;7.5;7.1;7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg27023313