To monitor the Bluemix Liberty runtime with JConsole, you must complete the following steps:
Push your application within a server package containing an appropriate server.xml.
Start the JConsole application with the appropriate system properties on the command line.
Provide the proper Remote Process url, Username, and Password to JConsole.
Here is more detail on each of the above steps.
1. Push the server package containing your application limiting it to a single instance. This is the default (-i=1). Your server.xml must contain the monitor-1.0 and restConnector-1.0 features. It also must contain a basicRegistry element and administrator-role element as shown below:
<user name="jconuser" password="jconpassw0rd"/>
</administrator-role> NOTE: The password should be encoded with the securityUtility tool provided with Liberty.
2. JConsole is included with your java installation. Go to <java-home>/bin (java 1.7 or higher) and run this command:
The truststore parameters will take the following defaults that should work in most cases: -J-Djavax.net.ssl.trustStore=<java-home>/jre/lib/security/cacerts -J-Djavax.net.ssl.trustStorePassword=changeit -J-Djavax.net.ssl.trustStoreType=jks
Specify appropriate truststore parameters if necessary.
3. Fill in the Remote Process field with this url: service:jmx:rest://<appName>.mybluemix.net:443/IBMJMXConnectorREST. Also fill in the Username and Password fields with an administrator-role role user and password from the server.xml. Click Connect.
The connection should succeed and JConsole will start monitoring.
If your connection fails, you can produce logs to help diagnose the problem. First, try collecting client side trace by adding this to the jconsole command: -J-Djava.util.logging.config.file=c:/tmp/logging.properties
Here is a sample logging.properties file: handlers= java.util.logging.FileHandler
java.util.logging.FileHandler.pattern = /tmp/jmxtrace.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
You can also add this to the jconsole comand: -J-Djavax.net.debug=ssl, which will produce SSL diagnostic tracing in a separate JConsole output window. Lastly, you can enable tracing on the server side by adding this to your server.xml: <logging traceSpecification="com.ibm.ws.jmx.*=all"/>
Hi Chris, great article… but I can’t access this service in my Liberty Server on Bluemix. I always get the same error:
mar 01, 2016 9:38:35 AM com.ibm.ws.jmx.connector.client.rest.internal.RESTMBeanServerConnection loadJMXServerInfo
GRAVE: CWWKX0203E: O cliente REST do Java Management Extensions do WebSphere recebeu um código de resposta 404 inesperado com a mensagem ‘Not Found’ a partir do servidor para a URL https://brf-app-core.mybluemix.net:443/IBMJMXConnectorREST na conexão rest:brf-app-core.mybluemix.net:443
Wanted to ask you, if there is a JMX endpoint exposed by Bluemix platform using which the performance of all the individual infrastructure components of the Bluemix platform such as the Cloud Controller, HAA etc could be monitored using JConsole or JMX ?
Vaadin Bakery App Starter is a proven full-stack reference application you can use as a starting point for many serious business web apps. It contains many commonly needed features, like RDBMS database accessed using solid JPA+EJB (or Spring) -based persistency and business layer, mindful authentication and authorization, and a UI code structure suitable for non-trivial, large-scale business applications.
Yantra transformed into an award winning Fintech powerhouse. Yantra Financial Technologies was recognized as a “Company to Watch” as part of the 2016 FinTech Forward rankings released by American Banker and BAI.
Have you wondered why rolling out features in your app is so difficult and time-consuming with very little or no feedback on how the newly released feature is performing? I bet you have. Well, you have an answer now – introducing Bluemix App Launch Service. Refer to the announcement