aspose file tools*
The moose likes BEA/Weblogic and the fly likes jconsole to weblogic using t3s Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "jconsole to weblogic using t3s" Watch "jconsole to weblogic using t3s" New topic
Author

jconsole to weblogic using t3s

Jukka Nevalainen
Greenhorn

Joined: Dec 14, 2009
Posts: 9
Hi there

I'm trying to get my jconsole connected to a weblogic (hotspot) instance in order to control an mbean. The mbeans is being registered, as the wls console logs the registration.
I've started the server using the following properties:
-Djmx.invoke.getters=true
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=7091
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Besides, I'm starting my jConsole like that:
jconsole.exe -J-Djava.class.path=C:\path\to\java\jdk160_16\lib\tools.jar;C:\path\to\java\jdk160_16\lib\jconsole.jar;C:\path\to\wls\bin\wl10.3b\wlserver\server\lib\wlfullclient.jar;C:\path\to\wls\bin\wl10.3b\modules\com.bea.core.descriptor.wl_1.2.0.0.jar -J-Djmx.remote.protocol.provider.pkgs=weblogic.management.remote -debug

I created the wlfullclient.jar with some kinda jarbuilder.jar.. (was somewhere included by the weblogic).

So then the JConsole Connection GUI is showing and I enter: localhost:7091 as the remote JMX Server. I actually can connect, but there are only four folders visible in the MBeans part, which are:
- JMImplementation
- com.sun.management
- java.lang
- java.util.logging

I also tried this URL: service:jmx:rmi:///jndi/rmi://127.0.0.1:7091/jmxrmi but nor does this one show any further mbeans.

I read on many sites on the internet about a similar problem accessing custom MBeans but nothing fixed my particular issue.

Help of any kind is appreciated.

Regards,
rethab

@Edit: It's doesn't necessarily need to be t3s as protocol. but that's the one i'm usually using
Vic Pezzolla
Greenhorn

Joined: Nov 08, 2009
Posts: 9
I have a similar problem and found a problem a couple of weblogic parameters being set to false. I made them true and was able to connect locally to my mbeans.

wls:/cds2.dev/edit/JMX/cds2.dev !> ls()
-rw- CompatibilityMBeanServerEnabled true
-rw- DomainMBeanServerEnabled true
-rw- EditMBeanServerEnabled true
-rw- InvocationTimeoutSeconds 0
-rw- ManagementEJBEnabled true
-rw- Name cds2.dev
-rw- Notes null
-rw- PlatformMBeanServerEnabled false <-------------------- set to false
-rw- PlatformMBeanServerUsed false <-------------------- set to false
-rw- RuntimeMBeanServerEnabled true
-r-- Type JMX

-r-x freezeCurrentValue Void : String(attributeName)
-r-x isSet Boolean : String(propertyName)
-r-x restoreDefaultValue Void : String(attributeName)
-r-x unSet Void : String(propertyName)
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jconsole to weblogic using t3s
 
Similar Threads
Problem with classpath
Retrieve WL command-line (-Dname=value)
question about weblogic 6.1
new domain with weblogic6.1 problem?
Error on remote debugging WebLogic 10 with Eclipse