In the previous post we focused on some useful runtime metrics, which are of interest when monitoring your application server and applications. This post introduces the management clients provided by the JBoss EAP / Wildfly Application Server to manage and configure server instances.
As announced this is the last post of our series about clustering of the Redhat EAP 6 and JBoss AS 7. The other posts of this series were
- Clustering in JBoss AS7/EAP 6
- Managing cluster nodes in domain mode of JBoss AS 7 / EAP 6
- Scalable HA Clustering with JBoss AS 7 / EAP 6
- Load-balancing and failover of remote EJB clients in EAP6 and JBoss AS7
- Clustering of the messaging subsystem HornetQ in JBoss AS7 and EAP 6
This post will dig deeper into the clustering mechanisms of the EAP 6 and JBoss AS 7. We will show different solutions to multicast problems you will get in most cloud networks as well as some other networks. Infinispan uses JGroups to do its cluster communication. Cluster communication here means multiple things: finding other cluster nodes, providing a reliable transfer, implementing multicast communication even if there is no IP multicast available, identifying dead cluster nodes and a little bit more. In fact JGroups is able to do a lot more but Infinispan does not need all of the opportunities JGroups offers. The upcoming HornetQ version 2.3 which will be included in the EAP 6.1 will use JGroups for server discovery too. This post will explain the basic principles of JGroups and how to configure it in different network setups, especially most cloud networks.
In the recent posts of this series we talked about many different aspects of clustering for the JBoss AS 7 and its quality assured version EAP 6, such as:
- the basic concepts,
- managing cluster nodes in domain mode,
- scalable HA cluster topologies and
- load-balancing and failover of remote EJB clients.
Until now, there is one important thing we have not covered yet: clustering of the messaging subsystem. The EAP 6 as well as the AS 7 uses HornetQ as default messaging provider. In this post we want to give an overview about the clustering abilities of HornetQ and explain how to use the various clustering features in combination with the EAP 6 or respectively the JBoss AS 7. We implemented a simple JMS client application to demonstrate the HornetQ clustering abilities.
After more than two years of development and one year after the release of the first community version, yesterday the JBoss Enterprise Application Platform 6.0.0 (EAP6) was published at the Red Hat customer portal. It is built around the new blazingly fast und thoroughly modular JBoss application server 7. It supports the full Java EE 6 profile and it is the first EAP version that provides a downloadable Maven repository. By adding it to your enterprise repository you can enjoy the same benefits for the development as with the community version.
The EAP 6.0.0 is built from the 7.1.2 development branch of the JBoss application server. The development of the community version switched to the 7.2.0 branch. Thus, the EAP will be continuously hardened for enterprise production environments whereas the community version will stay the focus for innovation.
The EAP 6.0.0 is available with a subscription from Red Hat. The subscription includes enterprise-class support SLAs, guaranteed patches, updates, hot-fixes, and legal assurance.
You can download a 30-days evaluation version of the EAP 6.0.0 from the Red Hat customer portal.
Since March 15th of the JBoss Enterprise Application Platform (EAP) is available in the Version 6 Beta. The EAP is based on the Java EE 6 certified JBoss AS 7.1 community release, which impresses not only by the fast start-up time and low memory consumption but also by its new clean architecture.
At the moment, the EAP 6 Beta is pretty close to the community version. It includes a few critical bug fixes and some brandings. The differences will be larger with the on going quality assurance and maintenance phase.