Accessing WLS MBeans (8.1 + 9.2)

Hello,
I'm currently porting an app from WLS 8.1 to 9.2.
One difference is the access to the WLS-Runtime-Konfiguration. In 8.1 we did this via weblogic.server.Server etc. Now in 9.2 I have to use the JMX conforming way described in http://e-docs.bea.com/wls/docs90/jmx/accessWLS.html.
My question is: Is there a way to access the runtime config that works in 8.1 AND 9.2?
(9.2 no longer supports the typesafe Interfaces and in 8.1 the runtime mbean server is not deployed at the same jndi node, if at all).
Any ideas?
Kai

I did some more research and found this solution:
As shown in
http://edocs.bea.com/wls/docs81/jmx/basics.html
you can still use the MBeanHome-Interface to access the Weblogic-MBean-Interfaces.
However, this method of access is deprecated and will probably be removed in 9.3 (as I have heard) so reimplementing the management mbean access will be inevitable.

Similar Messages

ApplicationLifeCycleListener can't access Runtime MBean Server

Hi all,
I have encountered quite a strange behaviour in Weblogic 9.0. I am actually trying to deploy an application originally developed on Weblogic 9.2 to Weblogic 9.0. Everything works fine, except the ApplicationLifeCycleListener. The Post Start method tries to register MBeans to the Runtime MBean Server and deregisteres them when the application stops in Pre Stop. In Weblogic 9.2, it works fine. I can access the MBean Server with a local connection as described here: [url http://e-docs.bea.com/wls/docs90/jmx/accessWLS.html#1119237]
The documentations on this for WL 9 and WL 9.2 do not differ significantly. Anyway, WL 9 quits any attempt to make local connections to the Runtime MBean Server with an Exception:
javax.naming.NameNotFoundException: While trying to look up comp/env/jmx/runtime in .; remaining name 'comp/env/jmx/runtime'
It works when I move the establishment of a connection into an EJB. I suppose that the ApplicationLifeCycleListener just can't see the Runtime MBean Server in Weblogic 9.0.
What do I do wrong? :-)
Thanks,
S?ren

I too am having problems accessing Directory server from Netscape Console installed on Winxp.
If I try to open Directory server it doesn't give any error. No windows nothing.
If I try th same from the machine on which it is installed everything is fine. What is strange is that it did open a couple of times. But at the same time I can open the admin server, Netscape Messaging server from the xp box. Searching all over for a solution. Any help/pointers would be greatly appreciated.
Config details:
iDS4.13, iMS 5.0, running on Sol 8 box
Netscape Console 4.2 on WinXP.
Thanks

Accessing an MBean Programmatically

Hi can anybody tell me how access an mbean by a sample program .
For example in case of jboss , the jboss-service.xml contains an entry like the following...
<mbean code="org.jboss.jmx.adaptor.rmi.RMIAdaptorService"
name="jboss.jmx:type=Connector,name=RMI">

<attribute name="JndiName">jmx/rmi/RMIAdaptor</attribute>

<attribute name="RMIObjectPort">0</attribute>

<attribute name="ServerAddress"></attribute>
</mbean>
From this I use the part ....
'<attribute name="JndiName">jmx/rmi/RMIAdaptor</attribute>'
i.e. my JNDI Name is jmx/rmi/RMIAdaptor
So in my code it is like ..
MBeanServerConnection server = (MBeanServerConnection) ctx.lookup("jmx/rmi/RMIAdaptor");
Now in case of JCAPS from where I can get the JNDI lookup string name ? If some one has any sample code or doc it will be very helpful for me .
Regards,
Ayan

To enable the JMX agent for local access, add the following JVM property:
-Dcom.sun.management.jmxremote
To enable remote monitoring a couple of other JVM Options need to be set:
-Dcom.sun.management.jmxremote.port=portNum
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
See also: http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.htm

Using the App Server DAS to access "my" MBeans on cluster servers

I am wanting to use JMX to access some custom MBeans that are on server instances that are participating in app server clusters. I figured the way to do this is by connecting to the DAS, but the service groups don't show within the DAS (like when using JConsole), I can access other AMX services, but not my custom ones. I can access my MBeans if I directly connect to the app servers.
Any ideas? I am trying to keep my jmx client from having to know physical location of the clustered servers, and only knowing about the DAS.
Thanks,
Scott

Hi,
I am not an Application Server expert so I won't be able to answer your question
directly - but maybe the article 'Managing and Monitoring Web Services in
Project GlassFish' could be of help:
http://developers.sun.com/prodtech/appserver/reference/techart/ws_mgmt.html
There's also the doc on docs.sun.com which you may already know:
Chapter 20 Using the Application Server Management Extensions
http://docs.sun.com/app/docs/doc/819-3659/6n5s6m5ck?a=view
If you still don't get your answer - you may also want to visit the glassfish project:
https://glassfish.dev.java.net/ (perhaps join its user's mailing list?)
or The Aquarium: http://blogs.sun.com/theaquarium which has lots of interesting
tips and articles.
Hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/roller/page/jmxetc

Accessing Portal MBeans?

Hi
I would like to access the Portal 4.0 MBeans via a client app. Here is my sample
program:
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, "t3://xxxx-1:7501");
env.put(Context.SECURITY_PRINCIPAL, "system");
env.put(Context.SECURITY_CREDENTIALS, "xxxx");
Context ctx = new InitialContext(env);
MBeanHome homeBean = null ;
homeBean = (MBeanHome)ctx.lookup(MBeanHome.JNDI_NAME + ".portalServer");
Set s = null;
Iterator iter = null;
WebLogicMBean wBean = null;
wBean = homeBean.getMBean("entityPropertyCache", com.bea.p13n.mbeans.CacheMBean.class.getName());
if (wBean != null)
System.out.println("It is " + wBean.getName());
When I run this code, I get the following exception:
Exception: javax.management.InstanceNotFoundException: portalDomain:Name=entityPropertyCache,Type=com.bea.p13n.mbeans.CacheMBean
(admin server:true)
Start server side stack trace:
javax.management.InstanceNotFoundException: portalDomain:Name=entityPropertyCache,Type=com.bea.p13n.mbeans.CacheMBean
(admin server:true)
     at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:120)
     at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:245)
     at weblogic.management.internal.MBeanHomeImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
Can the Gurus please tell me what I'm doing wrong? I have tried various routes to
access the MBeans but nothing seems to work. The command-line weblogic.Admin GET
yields no results either.
Thanks,
P Kesh

Use queryNames instead of queryMBeans. queryNames returns a Set of ObjectName rather than a Set of ObjectInstance.
�amonn McManus -- JMX Spec Lead -- http://weblogs.java.net/blog/emcmanus

How to access the MBeans in the WLS 7.0

Hi
I have to access MBeans in the WLS7.0 using Management API (weblogic.management.*).
Anyone could you tell me asap
Regards
Bala

Same as 6.1..refer to the management and jmx thread for examples..
"Raj" <[email protected]> wrote:
>
Hi
I have to access MBeans in the WLS7.0 using Management API (weblogic.management.*).
Anyone could you tell me asap
Regards
Bala

Error message when access WLS: active sockets and socket readers configuration

Hi,
I got the following error when I tried to access the WLS using a program to get
the mbeans data.
This error happens when I have 3 or more servers running ( 1 admin server, 2 or
more managed servers). With cluster with more than 2 servers running, this error
also occurs.
<Sep 10, 2001 8:35:01 PM CDT> <Warning> <JavaSocketMuxer> <There are: '3' active
sockets, but the maximum number of socket readers allowed by theconfiguration
is: '2', you may want alter your configuration.>
I creased the socket readers from 33% to 66%, but I still got the same error.
I'm using WLS version 6.0 sp2
My configuration is:
Execute Threads = 15,
Socket Readers = 33% or 66%
Does anyone know how to fix this ? I am really appreciate for any suggestions.
thanks,
Kieu

thank you, I just found out about setting those sockets using command line options
an hour ago. But thanks a lot.
-Kieu
Kaye Wilcox <[email protected]> wrote:
Kieu,
You could try increasing the number of execute threads, you can do this
via
the admin console on the <server> --> Tuning tab.
See http://edocs.bea.com/wls/docs60/perform/WLSTuning.html#1104317 for
guidelines on setting the thread pool size and the number of socket readers.
Here is a link that talks about socket communication in a cluster
http://edocs.bea.com/wls/docs60/cluster/features.html#1007001.

Question about accessing Runtime MBean server

I would like to access the Runtime MBean server, and I've read this link: http://e-docs.bea.com/wls/docs91/jmx/accessWLS.html#1119237
I want to access this from within my EJB application. My WLS 9.1 setup is simple (it's a Single Server Domain), and the class which is attempting to get to the runtime MBean server is from a stateful session bean. The Bean class is in a Jar which is deployed within an Ear as part of an ELB module.
After reading "If the classes for the JMX client are located in a J2EE module, such as an EJB or Web application, then the JNDI name for the Runtime MBeanServer is", I expected to use the JNI name java:comp/jmx/runtime. But this failed.
What worked was the other address specified (java:comp/env/jmx/runtime).
So, apparently this means that "If the classes for the JMX client are located at the top level of an enterprise application (that is, if they are deployed from the application's APP-INF directory)"
So, I'm not sure what this means? Can someone clarify when each address is available and when it's not? The existing explaination in the doco doesn't make sense to me. My application is defined as part of an EJB module, yet I can't use the JNI name for an EJB module?
Thanks for any help,
Ed

It's called DNS registration.
You need to talk with your network engineers or someone who manages your public website.
We did our DNS registration of our Portal site through the telecom company who provides our office with Internet access.
Our portal URL from the Internet is:
https://portal.opnext.com/pls/portal
If you can access it and want to log in using our "demo" ID, please send me an e-mail requesting the password.
Eric
[email protected]

ADF application to access WLS data source .

Hi,
I have developed an ADF application in Jdeveloper 10.3.3 and deployed on Weblogic server. Now I want my application to access the data from data source created in WLS. I have created a data source (ds_demo) using the WebLoigc server option Services -> JDBC -> Data Sources.Target has been set to the default server where application is running.
Now I want application to access the database over the data source ds_demo. How can I do that?. Please provide any pointers.
Thanks & Regards,
MB

You should be able to use Java code like this to directly obtain the WLS data source if you're using a POJO/DAO :
Context ctx = null;
DataSource ds;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
ctx = new InitialContext(ht);
ds = (DataSource)ctx.lookup("DataSourceJNDINameHere");
This assumes you're deploying this on the same server hosting the datasource and that it's on port 7001.

Accessing Runtime Mbeans from the command line.

Hi,
I just wanted to know if runtime Mbeans can be invoked from the command line.
I tried accessing the ExecuteQueueRuntime mbean from the command line but nothing ever comes back.I am able to retrieve configuration mbeans without errors.
Do I need to create the runtime mbeans before I can use them ?
Or I need to invoke these commands via server code only?
Thanks.

Can you post the command you are using? I just tried this and seems to work.
D:\>java weblogic.Admin -username weblogic -password weblogic get -type ExecuteQueueRuntime -pretty
MBeanName: "mydomain:Location=myserver,Name=weblogic.admin.RMI,ServerRuntime=myserver,Type=ExecuteQueueRuntime"
CachingDisabled: true
ExecuteThreadCurrentIdleCount: 2
ExecuteThreadTotalCount: 3
ExecuteThreads: [Lweblogic.management.runtime.ExecuteThread;@3eb934
Name: weblogic.admin.RMI
ObjectName: weblogic.admin.RMI
Parent: myserver
PendingRequestCurrentCount: 0
PendingRequestOldestTime: 1129990444704
Registered: false
ServicedRequestTotalCount: 87
Type: ExecuteQueueRuntime
MBeanName: "mydomain:Location=myserver,Name=weblogic.kernel.System,ServerRuntime=myserver,Type=ExecuteQueueRuntime"
CachingDisabled: true
ExecuteThreadCurrentIdleCount: 5
ExecuteThreadTotalCount: 5
ExecuteThreads: [Lweblogic.management.runtime.ExecuteThread;@2cfc8c
Name: weblogic.kernel.System
ObjectName: weblogic.kernel.System
Parent: myserver
PendingRequestCurrentCount: 0
PendingRequestOldestTime: 1129990444754
Registered: false
ServicedRequestTotalCount: 124
Type: ExecuteQueueRuntime
MBeanName: "mydomain:Location=myserver,Name=weblogic.kernel.Non-Blocking,ServerRuntime=myserver,Type=ExecuteQueueRuntime"
CachingDisabled: true
ExecuteThreadCurrentIdleCount: 0
ExecuteThreadTotalCount: 0
ExecuteThreads: [Lweblogic.management.runtime.ExecuteThread;@2d125d
Name: weblogic.kernel.Non-Blocking
ObjectName: weblogic.kernel.Non-Blocking
Parent: myserver
PendingRequestCurrentCount: 0
PendingRequestOldestTime: 1129990444764
Registered: false
ServicedRequestTotalCount: 0
Type: ExecuteQueueRuntime
MBeanName: "mydomain:Location=myserver,Name=weblogic.admin.HTTP,ServerRuntime=myserver,Type=ExecuteQueueRuntime"
CachingDisabled: true
ExecuteThreadCurrentIdleCount: 2
ExecuteThreadTotalCount: 2
ExecuteThreads: [Lweblogic.management.runtime.ExecuteThread;@2d260e
Name: weblogic.admin.HTTP
ObjectName: weblogic.admin.HTTP
Parent: myserver
PendingRequestCurrentCount: 0
PendingRequestOldestTime: 1129990444814
Registered: false
ServicedRequestTotalCount: 0
Type: ExecuteQueueRuntime
MBeanName: "mydomain:Location=myserver,Name=weblogic.kernel.Default,ServerRuntime=myserver,Type=ExecuteQueueRuntime"
CachingDisabled: true
ExecuteThreadCurrentIdleCount: 15
ExecuteThreadTotalCount: 15
ExecuteThreads: [Lweblogic.management.runtime.ExecuteThread;@2d3a8c
Name: weblogic.kernel.Default
ObjectName: weblogic.kernel.Default
Parent: myserver
PendingRequestCurrentCount: 0
PendingRequestOldestTime: 1129990444854
Registered: false
ServicedRequestTotalCount: 7
Type: ExecuteQueueRuntime
D:\>
Thanks,
-satya
BEA Blog: http://dev2dev.bea.com/blog/sghattu/

Accessing the MBean for ProcessRuntime(WLI) through WLST

Since the cmo is not available for Custom MBeans and WLI MBeans are custom, how can I access or execute the methods for the MBean from WLST. I guess I can probably do it with the invoke command but the sytax foroperation invocation is not that intuitive. Is there another way i can access the ProcessRuntime Bean and invoke the methods directly.
Thanks.

Marc,
This is just a guess(have'nt done this), but I think the settings are not an exception, and you should be able to find the MBean here:
http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_intro.htm#BHCCJJED
This section of the doc seems to walk through an example setting properties in adf-config.xml
I would interpret those instructions in the official doc to mean :
1. If you don't mind changing this at deploy time and re-deploying(like we do when we're in deep development), you can change this and redeploy.
2. If you have a deployed application, you can make changes through WLST. But keep in mind that the changes you make through WLST will not be overwritten later when you change the adf-config in Jdev and redeploy.
(This lets you fine tune the timeouts for specific environments. ex: bigger timeouts for dev envs hosted with smaller resources/unstable un-optimized code, rather than guess a timeout that works for all environments )
Now comes the conflicting parts :
"If you must modify these properties, post deployment, you must edit adf-config.xml manually."
I think,they mean "manually using WLST". This can probabaly be done with both WLST commands and the MBeans.
Now once you make these changes to a deployed application, the changes you made are stored in MDS. This means that this "tuning" will survive a re-deployment.
So if we :
set the timeout to 1 minute initially at design time,
then change that to 5 minutes through WLST,
and then edit adf-config again in Jdev to a 10 minute value and redeploy,
the MDS still has the 5 minute value, and it will overwrite the 10 minute value we set later at design time and redeployed.
MDS documents are always applied on top of the deployed stuff.
The doc you refered to : http://docs.oracle.com/cd/E17904_01/webcenter.1111/e12405/wcadm_app_config_files.htm#CHDGEDGJ
does make a good explanation of how the changes persisted in MDS affects the final configuration.
Hop that helps !

Accessing WLS performance info.

WebLogic Server services can be accessed through T3ServicesDef interface.
Is there any way to access the WLS performance(Heap and other info displayed on WebLogic Console myserver properties tab) through a program.
thanks

Thanks so much, though i still have two questions:
1) Can I see the weblogic.common.managedobject.* API somewhere, since it is not available on Weblogic site..
2) And I don't know what you mean by
Oh, and when you use the Console to explore the naming tree it shows you names of interfaces objects
implement, for example weblogic.server.myserver implements
weblogic.common.managedobject.RemoteHelpInfoDef
Please elaborate if you get a chance......
Regards
Dimitri Rakitine <[email protected]> wrote:
javadocs:
http://www.weblogic.com/docs51/classdocs/javadocs/index.html
managedobjects:
From the 'Running the WebLogic Console' (http://www.weblogic.com/docs51/admindocs/console.html)
Details about WebLogic's services are displayed as "managed objects" in the Console. When an object is "managed" -- that is, when it implements a particular interface -- information about the object shows up in various displays in the Console. A ManagedObject may be database connection pools, security realms, EJB deployments and beans, or a variety of other subsystems and their components.. Oh, and when you use the Console to explore the naming tree it shows you names of interfaces objects
implement, for example weblogic.server.myserver implements
weblogic.common.managedobject.RemoteHelpInfoDef
weblogic.common.managedobject.ManagedObjectDef
weblogic.common.managedobject.TreeDef
weblogic.ejb isA EJBManager, weblogic.cluster.mycluster isA RemoteHelpInfoDef, ManagedObjectDef, TreeDef,
RemoteEquivalent etc.
Dimitri
http://dima.dhs.org

Error while accessing ProcessRuntime mBean

Hi,
I am getting the following error when I am trying to call the method "getProcessInstances()" on ProcessRuntime MBean.
[ m_process_runtime_mbean.getProcessInstances( query )).getInstanceIds() ); ]
----error---
[java] weblogic.management.ManagementRuntimeException: javax.management.Ope
rationsException: no such operation: getProcessInstances
[java] at com.bea.wli.management.runtime.ProcessRuntimeMBean_Stub.getPr
ocessInstances(Unknown Source)
Any of you have faced this problem ?
Thanks in advance,
Savitha

Hi user;
Its not certified to login EBS from linux client
Please check:
Linux-cleint (ebs) certification
pluggins
Hope it helps
Regard
Helios

Java 1.5 client with WLS 8.1 MBeans...

Hi,
          I maintain http://www.hermesjms.com and am investigating a problem with Hermes, which uses a 1.5 VM, interrogating WLS MBeans with WLS on 1.4.
          This thread describes what users have seen and what I have also replicated:
          http://www.hermesjms.com/forum/viewtopic.php?t=126
          As you can see, setting -Djmx.serial.form=1.0 fixes the serialisation problem but I now get the InstanceNotFoundException.
          I invoke getMBean() from the getStatistics() method here:
          http://cvs.sourceforge.net/viewcvs.py/hermesjms/Hermes4/src/java/hermes/ext/weblogic/WebLogicJMSAdmin.java?view=markup
          Any kind soul out there know what the problem may be? I'm kinda confused...
          Many thanks,
          Colin.

Hi Tom,
          When I upgrade to 9.0 client against 8.1 server I get the exceptions at the end of this mail. The server I am talking to is a single server, not in a cluster, and is just the out-of-the-box WLS 8.1 with a JMS server and some queues and topics configured.
          I don't get the ClassNotFoundException for WebLogicObjectName as this exists in weblogic.jar. Is there anything I need to do to WLS 8.1 to allow a 9.0 client to interop?
          Cheers,
          Colin.
          2005-08-04 08:25:41,753 [Timer-7] DEBUG hermes.ext.weblogic.WebLogicJMSAdmin - Constructed JMSDestination MBean name: mydomain:JMSServerRuntime=MyJMS Server,Location=myserver,Name=MyDistributed Queue,ServerRuntime=myserver,Type=JMSDestinationRuntime
          2005-08-04 08:25:41,773 [Timer-7] ERROR hermes.HermesWatchManager - Unexpected Exception
          weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception
               at weblogic.management.internal.MBeanHomeImpl_814_WLStub.getMBean(Unknown Source)
               at hermes.ext.weblogic.WebLogicJMSAdmin.getMBean(WebLogicJMSAdmin.java:329)
               at hermes.ext.weblogic.WebLogicJMSAdmin.getStatistics(WebLogicJMSAdmin.java:155)
               at hermes.ext.weblogic.WebLogicJMSAdmin.getDepth(WebLogicJMSAdmin.java:119)
               at hermes.impl.HermesAdminAdapter.getDepth(HermesAdminAdapter.java:108)
               at hermes.impl.DefaultHermesImpl.getDepth(DefaultHermesImpl.java:1187)
               at hermes.HermesWatchManager.updateWatchStatistics(HermesWatchManager.java:202)
               at hermes.HermesWatchManager.doUpdate(HermesWatchManager.java:170)
               at hermes.HermesWatchManager.access$000(HermesWatchManager.java:38)
               at hermes.HermesWatchManager$2.run(HermesWatchManager.java:84)
               at java.util.TimerThread.mainLoop(Timer.java:512)
               at java.util.TimerThread.run(Timer.java:462)
          Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
               java.lang.ClassNotFoundException: weblogic.management.interop.WebLogicObjectName: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
               at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
               at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:155)
               ... 12 more
          Caused by: java.lang.ClassNotFoundException: weblogic.management.interop.WebLogicObjectName: This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on all other members of that cluster
               at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:344)
               at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:258)
               at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:253)
               at weblogic.rjvm.MsgAbbrevInputStream.resolveClass(MsgAbbrevInputStream.java:327)
               at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.resolveClass(ChunkedObjectInputStream.java:316)
               at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
               at java.io.ObjectInputStream.readClassDesc(Unknown Source)
               at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
               at java.io.ObjectInputStream.readObject0(Unknown Source)
               at java.io.ObjectInputStream.readObject(Unknown Source)
               at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:120)
               at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:120)
               at weblogic.management.internal.MBeanHomeImpl_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
               at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
               at java.lang.Thread.startThreadFromVM(Unknown Source)
          2005-08-04 08:25:41,773 [Timer-7] DEBUG hermes.HermesWatchManager - closing Hermes WebLogic
          2005-08-04 08:25:41,783 [Timer-7] DEBUG hermes.impl.jms.ThreadLocalSessionManager - all sessions closed, closing Connection

Jconsole can't access MBeans in windows XP

I developed a sample Mbean and started in windowsXP. when i started jconsole it is not showing any java process. but the same code runs in linux fine. The jconsole in the windows xp can access the MBeans running in Linux . My temp dir is in FAT32. I tried to acees the MBeans running in windows XP using jconsole in linux but that was in vain. I disabled authentication and ssl.
plz help me!!!!!!!!!!!!!!!

Hi,
Sorry for the late reply - with the summer time it seems that many messages
have slipped through my attention ;-(
I cannot answer your question directly for lack of information on the specific
problem you're experiencing.
You may want however to use the information provided here:
http://blogs.sun.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole
in order to figure out what is happening.
If your agent has security enabled you may want to have a look at the new
JMX advanced example that's been added to JDK 6 build 96 (you will need
JDK 6 to run the example) - see here:
http://blogs.sun.com/jmxetc/entry/an_advanced_jmx_example_for
Hope this helps,
-- daniel

Accessing WLS MBeans (8.1 + 9.2)

Similar Messages

Maybe you are looking for