Possible solutions if the application you want to monitor does not appear in the connection dialog list.
Before any application can be monitored, the Java™ Virtual Machine (JVM) it is running on must have a Health Center agent installed. See the agent installation instructions.
Check the Health Center agent installation. See Installing the Health Center agent for more information.
Check that the application has been enabled for monitoring. See Starting a Java application with the Health Center agent enabled for more information.
Check the application to see if it has been started. Check that the agent is running on the application. If the agent has started successfully, you normally see a message like INFO: Health Center agent started on port 1972 in the application console. The port number is also written to the healthcenter.<pid>.log file in the users temporary directory. The <pid> is the process ID for the agent that is listening on that port.
Check that the application is still running. Sometimes applications end unexpectedly early.
Connection problems are also possible if the monitored Virtual Machine (VM) is running, but there are no more live application threads.
If the monitored VM has been suspended, the connection dialog cannot connect to the monitored VM and might timeout.
When the monitored application is not on the same workstation as the client, the client must be able to access the monitored application remotely. If the remote workstation is protected by a firewall, a port must be opened in the firewall to enable the Health Center agent to listen for connections. Firewalls can also cause timeouts when scanning for Health Center agents on a remote machine. In these cases, specify the exact Health Center port, and clear the Scan next ports for available ports option.
-Djava.rmi.server.hostname=<preferred_ip_address>The <preferred_ip_address> determines the interface used by the agent.
If authentication is enabled on the monitored application, ensure that security credentials have been entered on the first page of the connection wizard. Without these credentials, the monitored application might not appear in the application list on the second page of the connection wizard.
-agentlib:healthcenter=keepAlive