Connection Failures
Installed Settings
MC4J uses the InstallAnywhere installer and launcher system to provide for platform integration. There is a file "MC4J <version>.lax" where you can alter the configured JVM to start MC4J or change its startup settings such as the heap size. Use "lax.nl.current.vm" to set the path to the Java executable of your choice. You can add a property "lax.nl.java.option.additional" to add jvm options like heap size. An example is shown below.
Can't select server installation
The latest versions of MC4J attempt to automate the import of the necessary server jars by finding them within the installation directories. This works by assuming the location of the jars are based on a typical installation. If these jars are moved or if the server vendor rearranges them, MC4J may have trouble find the necessary jars. The only current workaround is to make sure they are arrange as inspected, though other solutions are being investigated.
javax.net.ssl.SSLHandshakeException
While connecting to a server utilizing JMX Remoting, if you receive a ConnectIOException with a nested exception of javax.net.ssl.SSLHandshakeException you'll need to disable the use of SSL on the connection. With the JDK 1.5 built in remoting you can set the sytem property com.sun.management.jmxremote.ssl=false or you can uncomment the same line in your jdk install at jre/lib/management/management.properties.
C ben poche !
For this to work you need to pai up with..
com.sun.management.jmxremote.authenticate+false
if you do not then you get a jvm exit error