Originally published on 15 Dec 2015
Last updated on 09 Oct 2019
Many of our customers often use a different JMS provider in their organisation than the embedded JMS broker shipped with Payara Server, for example IBM MQSeries or ActiveMQ. Doing this often caused problems for our customers because the unconfigured OpenMQ broker could cause start up problems or delays, as well as delays in XA recovery. From Payara Server 4.1.154 onwards we've added functionality to disable the embedded OpenMQ broker. In this blog we'll talk through how to disable OpenMQ across the whole domain.
JMS Broker to DISABLED
We've added a new Broker type of DISABLED to the administration. For each base configuration you use in your domain set the configuration type to DISABLED.
(click to enlarge)
In the image above we are setting the Broker to disabled for the Configuration server-config. You should do this for all of your server configurations.This can also be done using the command line by running;
asadmin set configs.config.server-config.jms-service.type=DISABLEDasadmin set configs.config.default-config.jms-service.type=DISABLED
where the section in bold is the name of your configuration.
Delete the JMS Resources
Once you have set the embedded broker to disabled the various JMS resources can be deleted.First delete the JMS Connection Factory
The OpenMQ broker also has a Resource Adapter (jmsra) deployed which is used to integrate MDBs into JavaEE applications. The resources associated with this resource adapter should also be removed.
This can be done from the command line in one go by running:
delete-connector-connection-pool --cascade jms/__defaultConnectionFactory-Connection-Pool
Finally the JMS resource adapter can be deleted by deleting the directory rm -rf <payara-install-dir>/glassfish/lib/install/applications/jmsra
where <payara-install-dir> is the root of your Payara installation.
Remove JMS from the console
After all the steps above the JMS broker is disabled in your configuration. If you wish to go further, it is possible to remove the OpenMQ specific JMS sections from the administration console. To do this delete the administration console jms plugin.rm -rf <payara-install-dir>/glassfish/modules/console-jms-plugin.jar
As you can see from the screenshot above there is now no Java Message Service section in the console.
That's all there is to it! Now the OpenMQ Broker has been disabled within your Payara domain.
Related Posts
Payara Server's High Availability Architecture: A Quick Technical Overview
Published on 05 Jun 2024
by Luqman Saeed
2 Comments
Introduction
In today's business world, competition is fierce and relentless. As a result, maximizing uptime while reducing downtime and its expenses is a top priority. In particular, users now expect applications to deliver consistent ...
Watch webinar recording - Mastering Java Message Service: A Jakarta EE Developer's Guide
Published on 15 Apr 2024
by Chiara Civardi
0 Comments
Asynchronous communications are an essential elements of flexible and scalable Jakarta EE applications, as they can support the independent processing of multiple tasks, leading to improved performance and responsiveness. This webinar with Petr ...