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:
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_18.104.22.168.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:
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.
@Edit: It's doesn't necessarily need to be t3s as protocol. but that's the one i'm usually using