Accessing Weblogic Server 9.2 Platform MBeans with JConsole

In order to get the 1.5 jConsole to connect to Weblogic's JMX service it requires a number of tweaks to the server.

These changes can easily be made via the Admin console found at http://localhost:7001/console (assuming the server is on localhost and using port 7001).

To login you will need the username/password configured during the domain creation.
Two key changes are required to make the domain work: Allowing anonymous JMX access and enabling IIOP

Step by step
To enable the anonymous JMX access goto the domain - then security table then general and tick the AnonymousAdminLookup? check box. Save the setting (you'll have to lock the domain to edit it).
Next click on the server, then settings then the protocol tab then IIOP and select enable IIOP and also add in a username and password. It doesn't matter what these values are but it needs them to be set even when using anonymous access!
Save and activate these changes (you may need to visit another tab to pesuade Weblogic to save properly).
Finally restart the server.
Then on the command line enter jConsole - select the Advanced tab and enter a JMX Url of service:jmx:rmi:///jndi/iiop://192.168.0.210:7010/weblogic.management.mbeanservers.runtime you should be able to leave the username/password blank.
You should be able to see a tree of the available JMX Beans in the server.

Troubleshooting

If there are a large number of MBeans in your monitored application, you may run into a problem using Windows where the IIOP connection will timeout. You may see an error like this:

Internal communication failed. (in getResults) org.omg.CORBA.COMM_FAILURE:
vmcid: SUN minor code: 208 completed: Maybe

In this case you can set the com.sun.CORBA.transport.ORBTCPReadTimeouts property to adjust the transport read tcp timeout property, which is a colon separated property with the following syntax.

If you are getting this error, then you can add this option to the jconsole command line, adjusting the 2nd value higher as needed. This example sets the timeout to 30 seconds:

jconsole -J-Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=10:30000:500:10