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 chari...@wso2.comwrote:
Noted.
On Thu, Jul 5, 2012 at 10:40 AM, Amila Maha Arachchi ami...@wso2.comwrote:
Hi all,
$subject? I tried to
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,
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
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 ami...@wso2.com 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
Hi Vijitha,
Thanks for the tip. I have missed that one. Actually I didn't know about
it. So, after replacing localhost with my IP in the jmx.xml it works fine.
Sorry about the false alarm.
Regards,
AmilaM.
On Thu, Jul 5, 2012 at 2:07 PM, Vijitha Kumara viji...@wso2.com wrote:
Have you
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
Noted.
On Thu, Jul 5, 2012 at 10:40 AM, Amila Maha Arachchi ami...@wso2.comwrote:
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
