Troubleshooting JMX configuration for Liberty profile

Troubleshooting JMX configuration for Liberty profile

When we start the MPF Admin Services and the MobileFirst runtimes, we can encounter several exceptions in the Liberty profile server logs.

profile: errors. Table that describes multiple errors that you might receive when you try to configure the Liberty profile
Message title Error Cause Resolution
Invalid administrator user Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: CWWKX0215E: There was a problem with the user name or password provided. The server responded with code 401 and message 'Unauthorized' The value of the ibm.worklight.admin.jmx.user JNDI property is not an administrative Liberty profile user. Edit the server.xml file and make sure the user referenced in ibm.worklight.admin.jmx.user is defined in the <administrator-role> element.
SSL socket factory not found Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: java.lang.ClassNotFoundException: Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory The IBM JDK cannot be used with the SSL socket factories of WAS Liberty profile. For information about resolving this issue, see Configure Liberty profile when IBM JDK is used.
No JMX connector configured Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: No JMX connector is configured The host name or the port number that is required for the JMX connection is not configured. Edit the server.xml file and make sure that both the ibm.worklight.admin.jmx.port and the ibm.worklight.admin.jmx.host JNDI properties are defined.
Read timed out Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: Read timed out The JMX connection times out before the operation completes. By default, the JMX connection times out after one minute. Edit the Liberty profile jvm.options file and add the following property:
Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=time in milliseconds

Default is 60000. Use a greater value. The following example uses three minutes.
Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=180000

Invalid certification path Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target The SSL configuration of the Liberty profile server is not correct. See Configure secure JMX connection to the Liberty profile.
Connection exception java.net.ConnectException: Connection refused: connect The JMX connection fails. Edit the server.xml file. Make sure that both the ibm.worklight.admin.jmx.port and the ibm.worklight.admin.jmx.host JNDI properties reference the local host, and that the https port number is defined in the <httpEndpoint> element.

Parent topic: Configuration of the application server

Message title	Error	Cause	Resolution
Invalid administrator user	Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: CWWKX0215E: There was a problem with the user name or password provided. The server responded with code 401 and message 'Unauthorized'	The value of the ibm.worklight.admin.jmx.user JNDI property is not an administrative Liberty profile user.	Edit the server.xml file and make sure the user referenced in ibm.worklight.admin.jmx.user is defined in the <administrator-role> element.
SSL socket factory not found	Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: java.lang.ClassNotFoundException: Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactory	The IBM JDK cannot be used with the SSL socket factories of WAS Liberty profile.	For information about resolving this issue, see Configure Liberty profile when IBM JDK is used.
No JMX connector configured	Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: No JMX connector is configured	The host name or the port number that is required for the JMX connection is not configured.	Edit the server.xml file and make sure that both the ibm.worklight.admin.jmx.port and the ibm.worklight.admin.jmx.host JNDI properties are defined.
Read timed out	Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: Read timed out	The JMX connection times out before the operation completes. By default, the JMX connection times out after one minute.	Edit the Liberty profile jvm.options file and add the following property: Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=time in milliseconds Default is 60000. Use a greater value. The following example uses three minutes. Dcom.ibm.ws.jmx.connector.client.rest.readTimeout=180000
Invalid certification path	Failed to obtain JMX connection to access an MBean. There might be a JMX configuration error: com.ibm.jsse2.util.h: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target	The SSL configuration of the Liberty profile server is not correct.	See Configure secure JMX connection to the Liberty profile.
Connection exception	java.net.ConnectException: Connection refused: connect	The JMX connection fails.	Edit the server.xml file. Make sure that both the ibm.worklight.admin.jmx.port and the ibm.worklight.admin.jmx.host JNDI properties reference the local host, and that the https port number is defined in the <httpEndpoint> element.