> Are you saying this based on your personal experience? > Or is this just an educated guess?
Whatever the cause, the end result is that javax.management.remote.JMXConnector does not exist. So the most likely culprits would be that CLASSPATH is different, or you're using a different JVM. For example, on many operating systems "java" is a wrapper that selects which JVM to use - possibly depending on environment variables. I can't speak to the comment about IBM and whether their JRE would be expected to include the JMX classes; but certainly some CLASSPATH or JVM mismatch seems likely. -- / Peter Schuller
