search

copper-engine / copper-monitoring

Monitoring GUI and server for COPPER
Apache License 2.0
5 stars 4 forks source link

Unnable to connect #2

Closed DanyHubGit closed 5 years ago

DanyHubGit commented 6 years ago

I have created a very simple Java application to test a simple workflow. The workflow starts and ends without any problem, but on monitoring UI I have always the same error "Unnable to connect" (with double n :) )

In my Java application I have referenced -copper-copperengine 5.0.1.jar -copper-jmx-interface5.0.1.jar -copper-monitoring-client4.2.0.jar -copper-monitoring-core4.2.0.jar

and I have set the following VM parameter in run configuration

-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.ssl=false

But I have always the same issue. It's possible to add a verbose log to understand why the GUI is in "unable to connect" state?

Is there any reference to add to Java application? Is there anything to instrument in my java code? Can you suggest me a checklist to understand how to resolve my issue?

Thanks in advance

image

HaydenHodge commented 6 years ago

Hello DanyHubGit. I would suggest figuring out where the communication breakdown is occurring. The best way to start would be by making sure your Java application has an exposed port with properly registered mbeans. Try testing that with JConsole, and making sure you can see your application's engines, processor pools, etc.

image

DanyHubGit commented 5 years ago

Thank you for your suggestions, there was an issue in my mbeans declarations.

HaydenHodge commented 5 years ago

No problem at all, I'm glad I could help!