Configuring HA-JMS on JBoss server cluster

After setting up the HTTP/HTTPS configuration for JBoss server cluster, the next assignment on my table was to set up the HA-JMS on the server cluster.

My JBoss installation folder structure is as below:

The “all” folder has everything configured for HA, however to understand the process, I have set up HA JMS within default folder. Go to the following folder JBOSS_HOME\server\default\deploy\jms

Remove all the files within the jms folder except jms-ra.rar. Please take a backup of these files some files might be required later. Within the default folder create a new folder named deploy-hasingleton within this folder create a sub-folder named jms. The contents of this folder will be similar to contents of the jms folder we had cleaned up earlier. The contents are as follows:

Check if the JBOSS_HOME\server\default\lib has the following two jars: jbossha.jar, jgroups.jar. If not add them from the JBOSS_HOME\server\all\lib folder.

Open the login-config.xml file from the folder JBOSS_HOME\server\default\conf.

Search for the following tag:

And change the dsJndiName to correct data source. Ensure that the name retains java:/ portion.

And in the second instance startup, the following logs are
created:

You can use a sample JMS client to insert messages in queue. You can verify that only one queue is created on the cluster and if the master server fails, the backup server will create the queue. The JMS client application will however need to know both the JNDI URLs i.e for the master and the slave. That intelligence will need to be built in by the developer. Please find below my JNDI client and jndi.properties file for your ready reference.

JNDI properties file contents:

01	package com.jms.test;

02

03	import javax.jms.JMSException;

04	import javax.jms.MessageProducer;

05	import javax.jms.Queue;

06	import javax.jms.QueueConnection;

07	import javax.jms.QueueSession;

08	import javax.jms.Session;

09	import javax.jms.TextMessage;

10	import javax.naming.NamingException;

11

12	public class JNDIClient {

13

14	public static void main(String[] args) {

15	// create a new intial context, which loads from jndi.properties file

16	javax.naming.Context ctx;

17

try {

18	ctx = new javax.naming.InitialContext();

19	// lookup the connection factory

20	javax.jms.QueueConnectionFactory factory

21	= (javax.jms.QueueConnectionFactory)ctx.lookup("ConnectionFactory");

22

23	// create a new TopicConnection for pub/sub messaging

24	QueueConnection conn = factory.createQueueConnection();

25	Queue queue = (Queue)ctx.lookup("queue/A");

26

27	Session session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);

28	MessageProducer producer = session.createProducer(queue);

29	TextMessage msg = session.createTextMessage();

30	msg.setStringProperty("Name", "Cooler Dude");

31	producer.send(queue, msg);

32

33	session.close();

34	conn.close();

35

36	} catch (NamingException e) {

37	e.printStackTrace();

38	} catch (JMSException e) {

39	e.printStackTrace();

40

}

41

42

}