Posts tagged JMS
When it comes to clustering and distributed computing performance, some of the challenges you have to overcome involve cache invalidation and coordination. Fortunately, both Payara Server and Payara Micro come with EclipseLink, which supports cache coordination and invalidation out of the box. This blog will explain how to configure this feature for your Payara Data Grid. We would also like to thank Sven Diedrichsen who is the community member that created the Hazelcast cache coordination.
Back in May, we announced the 172 release of Payara Server and mentioned a preview of our Maven plugin for Payara Micro, available on GitHub. Since then, we have released the plugin to Maven Central so, to illustrate it's use, I'll be revisiting my earlier blog on another feature of Payara Micro 172 - the ability to use Payara Micro as a JMS consumer.
Payara Micro 172 brings with it support for JCA adapters, meaning it can be used as a client for Java Messaging Service (JMS) brokers. JMS is a Java EE API which provides a common interface for standard communication protocols. This means that you can send and receive messages between systems in a platform and language independent way. With Payara Micro now supporting JMS, you can setup your Micro instance as a JMS client with Message Driven Beans (MDBs) to listen and respond to messages from other systems through a message broker.
This spring's silver lining, Payara Server 18.104.22.168, a highly cloud-focused release, is now available!
Focusing on enhancing Payara Server and Payara Micro's ease-of-use in cloud environments, we've brought in new features to make working with Docker more seamless and secure, native support for SaaS monitoring solutions and a huge increase in messaging capabilities for Payara Micro! Inside this quarter's release you will find 54 fewer bugs, a host of ecosystem and cloud improvements, and an update to match GlassFish 4.1.2. Carry on reading for a summary of this quarter's changes, or check out the full release notes for a complete list of changes.
Payara Server 171 was a huge release with lots of new features and improvements on many others. We've already written about improvements to the Request Tracing service and had a guest blog about using the email notifier.
The email notifier is just one of a whole host of notifiers we now have available. A lot were added in the 171 release and more are on their way in the imminent 172 release!
The new Java Magazine is out now, featuring a lot of useful articles about enterprise Java - not so much Java EE as a platform, but individual services that can be useful as part of a larger solution. See below for an introduction to my article on Custom Servlet Authentication Using JASPIC, also featured in the magazine.
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.