You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cloned the GIT repo and ran the JavaFX app against a NetBeans registered GlassFish 4.1.1.
Then I started the JavaFX app and clicked the Start button which caused the error.
In the GlassFish log:
Info: Retrieved JsonObject: null for InboundJaxrsResponse{context=ClientResponse{method=GET, uri=http://localhost:4848/monitoring/domain/server/jvm/thread-system/deadlockedthreads, status=404, reason=Not Found}} deadlockedthreads
Warning: A system exception occurred during an invocation on EJB MonitoringController, method: public void org.lightfish.business.servermonitoring.boundary.MonitoringController.gatherAndPersist()
The problem clearly is the 404 error for the REST URL.
Now it works after I activated monitoring. It appears that GlassFish has an initial state after installation where deadlockedthreads does not work. I could not reproduce the error later.
The text was updated successfully, but these errors were encountered:
I cloned the GIT repo and ran the JavaFX app against a NetBeans registered GlassFish 4.1.1.
Then I started the JavaFX app and clicked the Start button which caused the error.
In the GlassFish log:
Info: Retrieved JsonObject: null for InboundJaxrsResponse{context=ClientResponse{method=GET, uri=http://localhost:4848/monitoring/domain/server/jvm/thread-system/deadlockedthreads, status=404, reason=Not Found}} deadlockedthreads
Warning: A system exception occurred during an invocation on EJB MonitoringController, method: public void org.lightfish.business.servermonitoring.boundary.MonitoringController.gatherAndPersist()
The problem clearly is the 404 error for the REST URL.
BTW earlier catching of the 404 could be:
RestDataCollector
Now it works after I activated monitoring. It appears that GlassFish has an initial state after installation where deadlockedthreads does not work. I could not reproduce the error later.
The text was updated successfully, but these errors were encountered: