More info on remote jconsole connections

[update] the bug has now been fixed in our 10.1.3.1 code line so this will work out of the box in the coming 10.1.3.1 release.

It turns out that jconsole (which I never found the src to!) supplies the jmx credentials as a String array, such as:

String s5 = userNameUrl.getText().trim();
String s7 = passwordUrl.getText();
String as[] = { s5, s7 };
connectionparameters.map.put("jmx.remote.credentials", as);

whereas we were expecting the credentials to be in a Map.

I don't like to leave things hanging ... so I made some changes to the effected classes in an isolated view just to see if I could get it to work -- fear not, Product Managers don't touch production code!

With the changes in place, I was then able to get jconsole to connect remotely to both a OC4J standalone and an Oracle Application Server instance using their respective URL forms:

• service:jmx:rmi://[oc4j-host]:[oc4j-port]
• service:jmx:rmi:///opmn://[opmn-host]:[opmn-port]/[oc4j-name]

I've logged a bug and try and work this fix into the 10.1.3.1 release.

I also found once I'd connected that I needed a couple of extra libraries on the client side to make jconsole work fully -- javax77.jar to get the Stats classes and dms.jar.

Here's the set of Oracle libraries required:

• ${ORACLE_HOME}/j2ee/home/oc4jclient.jar
• ${ORACLE_HOME}/j2ee/home/lib/adminclient.jar
• ${ORACLE_HOME}/j2ee/home/lib/javax77.jar
• ${ORACLE_HOME}/dms/lib/dms.jar