Version

Argent Advanced Technology 5.1A-1707-G or below

Date

Thursday, 12 October 2017

Summary

Argent for Java failed to connect the JVMs running in JBoss AS/EAP 7.x

Technical Background

Argent for Java uses Java Management Extensions (JMX) technology to monitor an application running in a Java Virtual Machine (JVM)

The Managed Bean or MBean is the fundamental concept of the JMX API

The MBeans are Java objects that represent the manageable resources in the application running in the Java Virtual Machine

Each MBean is a collection of named and typed attributes that can be read and written

Argent for Java can monitor the MBeans of Java Virtual Machines(JVM) running in following Java based Application/Web servers:

• Apache Tomcat
• JBoss
• Glassfish
• WebLogic
• WebSphere

Argent for Java internally connects to a JVM using the following JMX JNDI service URL:

This URL uses RMI (Remote Method Invocation) protocol to connect to remote JVM

Our customers complained that Argent for Java failed to connect the JVMs running in JBoss EAP 7.0.5

According to JBoss documentation, from JBoss AS/EAP 7.x they had tighten the security

The previous JBoss versions allowed JMX connections without user authentications and we establish connection to JBoss JVMs using above URL that used RMI protocol

But from version 7.x onwards, the connection requires different vendor-specific-protocol and user authentication

The format of connection URL should be:

The issue has been addressed by enhancing the code to support all vendor-specific-protocols

Resolution

Upgrade to Argent Advanced Technology 5.1A-1710-A or above