Cluster Monitoring Data values not Display on Administration Console

[yoshioza]

Cluster Monitoring Data values not Display on Administration Console

Environment Details

• GlassFish Version (and build number): 7.0.9 (commit: 5860e42)
• JDK version: 17
• OS: Windows10
• Database: -

---

Problem Description

I am unable to monitor the status of clusters in the Administration Console.
It is possible to check using the asadmin command.

Steps to reproduce

1. Set up GlassFish (unzip to C:\glassfish).
2. Start GlassFish (use the command asadmin start-domain).
3. Access the Administration Console (localhost:4848).
4. Create a cluster.
5. Deploy the Sample Application to the cluster.
6. Set all Monitoring settings of the created cluster to HIGH.

7. Start the cluster.

8. Display the Sample Application page.
   

9. Attempt to check the state of Cluster instances from Monitoring Data.

Cluster Monitoring Data is not displayed.

• application
  

• server
  

• resource
  

• Monitoring Data for the DAS server is displayed.

• The result of obtaining cluster information using the asadmin command.
  

DAS_server.log

testcluster01_server.log

Impact of Issue

In the Administration Console, it is not possible to monitor cluster resource usage, including memory consumption.

[OndroMih]

I can reproduce on GlassFish 7.0.15-SNAPSHOT. I see the following exception in the log:

[#|2024-04-07T01:50:31.193947+02:00|WARNING|GF 7.0.15-SNAPSHOT|org.glassfish.jersey.server.ServerRuntime$Responder|_ThreadID=61;_ThreadName=admin-listener(2);_LevelValue=900;|
  An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper.
java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider for jakarta.ws.rs.client.ClientBuilder cannot be found
	at jakarta.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:75)
	at jakarta.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:86)
	at org.glassfish.admin.rest.utils.Util.getJerseyClient(Util.java:269)
	at org.glassfish.admin.rest.resources.MonitoringResource.getChildNodes(MonitoringResource.java:159)

[OndroMih]

The reason for the exception is that in Admin Console, the context classloader is an OSGI classloader for the bundle org.glassfish.main.core.kernel, which doesn't see the service loader file jakarta.ws.rs.client.ClientBuilder present in jersey-client.jar.

ClientBuilder works in an a normal application deployed to the server because the web app classloader finds the service loader file.