[
https://issues.jboss.org/browse/ISPN-4112?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-4112:
-------------------------------------
Originally this issue was caused by issues with performance on the availability check,
which was fixed by ISPN-4235. However ISPN-4235 also removed the ability for RHQ JMX
plugin to report a cache being down if it was stopped. So I added that back in and
optimized it for the performant way of doing the lookup, but not doing a wildcard query as
it used to.
Also I enhanced the RHQ JBoss plugin to also support a cache being DOWN if it is not
running, which we never had before.
Now they both should operate the same with regards to showing a cache UP or DOWN between
plugins.
RHQ library plugin: restart cache -- availability report DOWN but
cache running
-------------------------------------------------------------------------------
Key: ISPN-4112
URL:
https://issues.jboss.org/browse/ISPN-4112
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX, reporting and management
Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
Reporter: Tomas Sykora
Assignee: William Burns
Labels: 63gablocker
When we explicitly call STOP operation on particular cache using RHQ UI, this operation
is successfully issued and cache is stopped.
Then, we can issue START operation as well.
Cache is started but RHQ is still not-correctly reporting that cache is DOWN and
unavailable.
I will investigate this issue, this is just for proper heads up and for tracking
purposes.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)