-
1. Re: Browsing Remote MBeans - Some Missing!
dimitris Mar 11, 2005 4:38 AM (in response to burakbayramli)You are making a typical mistake here: you cannot register on the server, MBeans created on the client. You'll have to use one of the createMBean methods instead (i.e. use the MBeanServer on the server side as a factory)
-
2. Re: Browsing Remote MBeans - Some Missing!
burakbayramli Mar 11, 2005 4:54 AM (in response to burakbayramli)Actually the snippets are from server and client side, respectively. So they are running in the right place. The registration code runs under JBoss, the client code is another machine.
-
3. Re: Browsing Remote MBeans - Some Missing!
burakbayramli Mar 11, 2005 5:00 AM (in response to burakbayramli)And also, the output I seem to get comes from localhost, not the remove server I am trying to connect. This API behaves little odd; Is there a way around this?
Thanks, -
4. Re: Browsing Remote MBeans - Some Missing!
dimitris Mar 11, 2005 5:11 AM (in response to burakbayramli)Do you really see the MBeans you create through the jmx-console?
check out this similar forum posting:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=60669 -
5. Re: Browsing Remote MBeans - Some Missing!
burakbayramli Mar 11, 2005 5:30 AM (in response to burakbayramli)Yes, I do see my MBeans through jmx-console.
I also read the links you posted, and I changed the code to:
InitialContext ic = getContext("192.168.43.75:1099");
server = (MBeanServerConnection) ic.lookup("jmx/invoker/RMIAdaptor");
..
I still seem to get localhost somehow. My assumption was the Context is received from remote host JNP port, then we lookup the necessary adaptor.
Is my getContext method wrong?
I am on JBoss 4.0.1.
Thanks again, -
6. Re: Browsing Remote MBeans - Some Missing!
dimitris Mar 11, 2005 5:43 AM (in response to burakbayramli)Maybe this (solved) bug relates to your case:
http://jira.jboss.com/jira/browse/JBAS-1442 -
7. Re: Browsing Remote MBeans - Some Missing!
burakbayramli Mar 11, 2005 8:11 AM (in response to burakbayramli)I just upgraded to 4.0.1sp1, still the same problem. Should I apply the workarounds mentioned in any case? Any other ideas would be appreciated as well.
Thanks,