Have you changed the <CARBON_HOME>/repository/conf/etc/jmx.xml <HostName> to the correct value (i.e. ip)?
On Thu, Jul 5, 2012 at 1:51 PM, Amila Maha Arachchi <[email protected]> wrote: > Hi again, > > I tested this today also with ESB 4.0.3 pack. I followed two methods. > > NOTE: I am using an offset of 3 and I have replaced the localhost with my > IP in the below urls. > > 1) Enable both RMIRegistryPort and RMIServerPort - Then provided the jmx > url which we get at server startup to JConsole. But couldn't connect to the > server (credentials provided) > service:jmx:rmi://10.100.2.91:11114/jndi/rmi://10.100.2.91:10002/jmxrmi > > 2) Enabled only RMIRegistryPort (as mentioned in Charitha's blog). Then > also it was not successful. Even-though RMIServerPort was disabled, it > appeared in the jmx url as follows. > service:jmx:rmi://*10.100.2.91<http://10.100.2.91:11114/jndi/rmi://10.100.2.91:10002/jmxrmi> > **:2*/jndi/rmi://10.100.2.91<http://10.100.2.91:11114/jndi/rmi://10.100.2.91:10002/jmxrmi> > :10002/jmxrmi > > AmilaM. > > > On Thu, Jul 5, 2012 at 1:25 PM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi Hiranya, >> >> When we try to *remotely* monitor a WSO2 product instance, instructions >> in [1] (in my previous mail) failed. For example I try to monitor instance >> running in some other person's machine (no firewalls etc..). I hope I have >> followed the steps correctly. >> >> Regards, >> AmilaM. >> >> >> On Thu, Jul 5, 2012 at 1:11 PM, Hiranya Jayathilaka <[email protected]>wrote: >> >>> Hi Amila, >>> >>> Can you please explain which part of JMX monitoring is not working? >>> >>> Thanks, >>> Hiranya >>> >>> On Thu, Jul 5, 2012 at 10:54 AM, Charitha Kankanamge >>> <[email protected]>wrote: >>> >>>> Noted. >>>> >>>> >>>> >>>> On Thu, Jul 5, 2012 at 10:40 AM, Amila Maha Arachchi >>>> <[email protected]>wrote: >>>> >>>>> Hi all, >>>>> >>>>> $subject? I tried to follow some articles on how to remotely monitor >>>>> WSO2 products via JMX (with 3.2.3 packs) and it seems the instructions >>>>> mentioned in those articles are not working. One such article is [1]. But >>>>> there is a workaround which can be found at [2]. >>>>> >>>>> Charitha et al, please pay attention to this during your testing >>>>> cycles. If this is broken, we'll have to fix this before we release the >>>>> kernel. >>>>> >>>>> [1] >>>>> http://wso2.org/library/knowledge-base/2011/04/monitoring-wso2-esb-using-jconsole >>>>> [2] >>>>> http://maharachchi.blogspot.com/2011/02/monitoring-your-java-application-with.html >>>>> >>>>> Regards, >>>>> AmilaM. >>>>> -- >>>>> *Amila Maharachchi* >>>>> Technical Lead >>>>> Member, Management Committee - Cloud & Platform TG >>>>> WSO2, Inc.; http://wso2.com >>>>> >>>>> Blog: http://maharachchi.blogspot.com >>>>> Mobile: +94719371446 >>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Senior Technical Lead; >>> WSO2 Inc.; http://wso2.org >>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >> >> >> >> -- >> *Amila Maharachchi* >> Technical Lead >> Member, Management Committee - Cloud & Platform TG >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> > > > -- > *Amila Maharachchi* > Technical Lead > Member, Management Committee - Cloud & Platform TG > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Vijitha Kumara Senior Software Engineer; WSO2, Inc.; http://wso2.com/ email: [email protected] Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
