This content has been marked as final. Show 11 replies
Which versions of WLS and JRockit are you using?
Sometime relatively recently the WebLogic MBeans were made available as Platform MBeans, but I can't recall when. I think there is a way to configure WLS to use platform MBeans even in advance of that becoming the default behavior.
<Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
I've upgraded to Mission Control 4.0.1 as well in an attempt to see if that works better. I guess my confusion is why I don't see WebLogic specific MBeans in the MBean Browser within Mission Control. With the 4.0.1 release I see example triggers that use an MBean path "com.bea:ApplicationRuntime=stockEar,Name=examplesServer_/stock,ServerRuntime=examplesServer,Type=WebAppComponentRuntime" but I don't see any com.bea packages in the MBean Browser.
I would assume that from Mission Control I would be able to access the "JDBCSystemResourceMBean" and see it's attributes and operations but no luck. From the links you've posted (thanks for the MBean reference that's a great link) I'm gathering that I need to enable the WebLogic server to be configured as the "Platform MBean Server". Can this be set in the console?
Thanks for the taking the time to help.
If you don't see the "com.bea" package tree then you are running on the other MBeanServer (there are at least 2 running on WebLogic) - try the other one.
[EL Finer]: 2010-12-07 15:18:58.978--ServerSession(54608908)--Thread(Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads])--JMX MBeanServer instance found: [weblogic.management.jmx.mbeanserver.WLSMBeanServer@2e38454], # of beans: , domain: [base_domain] at index: .
The following page has some details on connecting to WebLogic via either JRMC or JConsole.
Note: I also have the "Anonymous Admin Lookup Enabled" flag set so you can see them in certain situations whether connecting to a local or remote process.
You should see something like the following screen capture for JRMC
So these should be the MBean Servers:
Domain Runtime MBean Server - weblogic.management.mbeanservers.domainruntime
Runtime MBean Server- weblogic.management.mbeanservers.runtime
Edit MBean Server - weblogic.management.mbeanservers.edit
I attempted to use a "Custom JMX Service URL" in JRockit Mission Control (the default is service:jmx:rmi:///jndi/rmi://<host>:<port>/jmxrmi) based on my belief that I need to connect to one of the MBean Server instances above but it doesn't like the URL's I've tried. service:jmx:rmi:///jndi/rmi://<host>:<port>/jndi/weblogic.management.mbeanservers.runtime
Based on the links you provided, I also tried setting the "Anonymous Admin Lookup" to true and restarted the server but still have the same result.
Also tried JConsole which connects but shows the same set of MBeans that JRMC shows.
Still seems like I'm missing something, shouldn't the default jmxrmi allow browsing of something within WebLogic?
Set the values as you indicated but received the following in startup:
<Dec 7, 2010 5:38:08 PM EST> <Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
If you want to eliminate this log error and do not need Platform MBeans to be available via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to false.>
So I would need to turn of the JRockit -XManagement which would then disable JRockit Mission Control from being able to connect?
Well, have you tried setting this JVM option as described in the message?
If you have an Oracle support contract, I would file a support case at this point. You're very close, you simply need someone to get you over the finish line. Good luck.
Thanks James, success!
Adding the parameter does allow JRMC to connect to the 10.3 server and view the com.bea packages within the MBean browser. I was able to also verify that this is a change in behavior between WLS 10.0 and 10.3. Connecting JRMC to a 10.0 server and these values are available by default. Thanks again for your assistance.