[infinispan-issues] [JBoss JIRA] (ISPN-4366) RHQ JMX plugin provides unstable availability check with extensive deployments

[William Burns (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Burns resolved ISPN-4366.
---------------------------------

    Resolution: Won't Fix


This is fixed by upgrade an dependency within RHQ itself that was causing full mbean scans which would cause timeouts on resource statuses.

> RHQ JMX plugin provides unstable availability check with extensive deployments
> ------------------------------------------------------------------------------
>
>                 Key: ISPN-4366
>                 URL: https://issues.jboss.org/browse/ISPN-4366
>             Project: Infinispan
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX, reporting and management
>    Affects Versions: 7.0.0.Alpha4
>            Reporter: Tomas Sykora
>            Assignee: William Burns
>              Labels: 63gablocker, rhq
>
> Availability check was greatly improved by changes introduced in https://issues.jboss.org/browse/ISPN-4236 and https://issues.jboss.org/browse/ISPN-4235.
> This works pretty well in case of one deployment of an embedded application on one application server, which is monitored by an agent.
> However, when we try to monitor more deployments by the same agent (app servers, switched ports, each one with its own deployment), the process of availability checking is unstable. 
> Cache managers / caches... are reported repeatedly UP and DOWN, UP and DOWN. See linked bugzilla with attached screenshots depicting this issue.
> I suspect higher number of MBeans to cause this problem. 
> When we deploy on 2 servers, one of them for example was able to stabilize availability check after 2 hours and then, it stays UP.
> During deployment in 2xdomain mode = 4 servers, availability check "is skipping, jumping" UP, DOWN, UP, DOWN... etc. again, see screenshots in BZ.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)