[infinispan-issues] [JBoss JIRA] (ISPN-4236) RHQ JMX plugin causes Cache/CacheManager to report as not available

[William Burns (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963851#comment-12963851 ] 

William Burns commented on ISPN-4236:
-------------------------------------

The PR has some changes for our plugin that should improve performance of the getAvailabilityCheck for both CacheManager and Cache.  The latter was especially harmed because every attribute would force retrieval of all mbeans every time.

Also RHQ already has a fix to reduce it's payload as well: https://github.com/rhq-project/ems/commit/ba1253a4030e68b435acc4019ca9e5a8cb0f12a2 and should be in the 1.3.5 version of the mc4j jar that is bundled with the jmx rhq plugin that RHQ distributes: https://github.com/rhq-project/ems/commit/7fcd48d80dee7fed102813afb8e365163901f3e7
                
> RHQ JMX plugin causes Cache/CacheManager to report as not available
> -------------------------------------------------------------------
>
>                 Key: ISPN-4236
>                 URL: https://issues.jboss.org/browse/ISPN-4236
>             Project: Infinispan
>          Issue Type: Bug
>          Components: JMX, reporting and management
>    Affects Versions: 7.0.0.Alpha3
>            Reporter: William Burns
>            Assignee: William Burns
>             Fix For: 7.0.0.Final
>
>
> With the update to use newer RHQ, the CacheManager and Cache sometimes report as being down when using library JMX plugin.  It looks like RHQ added some additional checks which just pushes the operation time over the default of 5 seconds.  This is to clean up our code a bit to make the availability check for efficient.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira