[infinispan-issues] [JBoss JIRA] (ISPN-1967) Expose CacheView string via JMX
Mircea Markus (JIRA)
jira-events at lists.jboss.org
Wed Apr 4 10:53:47 EDT 2012
[ https://issues.jboss.org/browse/ISPN-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mircea Markus updated ISPN-1967:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
this is now integrated on both master and 5.1.x.
> Expose CacheView string via JMX
> -------------------------------
>
> Key: ISPN-1967
> URL: https://issues.jboss.org/browse/ISPN-1967
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Affects Versions: 5.1.3.FINAL
> Reporter: Michal Linhard
> Assignee: Manik Surtani
> Fix For: 5.1.4.CR1, 5.1.4.FINAL
>
>
> The JGroups view and CacheView differs and this causes trouble finding out what state the CacheView is in during elasticity/reslience tests.
> My test controller is driven by JGroups view, there was this particular case where this lead to test failure, or better said wrongly controlled test.
> After node0002 was killed in view 7:
> http://www.qa.jboss.com/~mlinhard/hyperion/run53-elas-dist-basic/table.html
> the controller saw JGroups view: [node0003/default|5] [node0003/default, node0004/default]
> which maybe existed in JGroups layer but never in Infinispan - in infinispan there was partition {node0003} + {node0004}
> and therefore it went on with the test which lead to errors, among others ISPN-1965, might be caused by this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list