[JBoss JIRA] (ISPN-6553) Configuration to XML serializer
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-6553:
-------------------------------------
Summary: Configuration to XML serializer
Key: ISPN-6553
URL: https://issues.jboss.org/browse/ISPN-6553
Project: Infinispan
Issue Type: Feature Request
Components: Configuration
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 9.0.0.Final
Provide a configuration serializer which can convert a Configuration object to XML
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ]
Jiří Holuša commented on ISPN-6298:
-----------------------------------
I can confirm that this bug is fixed in upstream master.
> Network partition detection not working in mgmt console
> -------------------------------------------------------
>
> Key: ISPN-6298
> URL: https://issues.jboss.org/browse/ISPN-6298
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.2.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
>
> Page: Clusters -> select server group.
> When I create a network partition and go to the page above, I still see the cluster status as "started". According to https://issues.jboss.org/browse/ISPN-5768 , there should be something as "Degraded"
> I checked that the cluster is really partitioned. When I go to JConsole, I see in JGroups JChannel attributes, that the "view" is only partial. I also see in the server logs that servers correctly detected the split.
> When I go to homepage (or the "Status event" tab), I see in the "Latest Grid Events:" that the split happened, hence the mgmt console is able to correctly detect it elsewhere.
> Note that neither the status of a cache, which has configured partition handling to true, changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-5969) Number of max entries is not shown in cache statistics in mgmt console
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-5969?page=com.atlassian.jira.plugin.... ]
Jiří Holuša commented on ISPN-5969:
-----------------------------------
[~vblagojevic] I looked at it and neither the value nor the progress bar is present there at all. So the question might be: do we consider this resolution as a fix? :)
> Number of max entries is not shown in cache statistics in mgmt console
> ----------------------------------------------------------------------
>
> Key: ISPN-5969
> URL: https://issues.jboss.org/browse/ISPN-5969
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Beta1
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
>
> Page: Caches -> select cache container -> select some cache
> Even when the maximum number of entries is specified for the cache and management console correctly marks it as "Bounded", the cache statistics field "Max capacity" is still with value "TODO".
> Also the progress bar below it seems to be not working yet.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ISPN-6124) List of caches is sometimes visually corrupt
by Jiří Holuša (JIRA)
[ https://issues.jboss.org/browse/ISPN-6124?page=com.atlassian.jira.plugin.... ]
Jiří Holuša commented on ISPN-6124:
-----------------------------------
[~vblagojevic] Hi Vladimir, I found the root cause of this issue. In the cluster-view/cluster-view.html, there is the div with ng-repeat directive to list the caches according to filters:
{code}
<div class="col-xs-6 col-sm-4 col-md-2" ng-repeat="cache in filtered = (currentCluster.getCachesAsArray() |
filter: {name: searchNameQuery} | cacheTrait:traitCheckboxes | cacheType:typeCheckboxes)" ng-show="cache.show" on-finish-render="matchHeight()">
{code}
The thing that makes all the boxes the same height is the matchHeight() function. The bug is that this method is not called after every change of the filters. It is called after the first load of the page. I also tried to click on the filters (cache types) and I don't know but I cannot find any deterministic reason when the method is called then. Sometimes it's called after clicking "Invalidation" with checked "Local", sometimes not, I don't know. The key thing in here is that the matchHeight() must be called after filter change and re-rendering the cache list.
Unfortunately my AngularJS knowledge ends here, I don't know how to solve it, but I think it will be fairly easy for you, you just need to find out the right place, where to put it :)
> List of caches is sometimes visually corrupt
> --------------------------------------------
>
> Key: ISPN-6124
> URL: https://issues.jboss.org/browse/ISPN-6124
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.1.0.Final
> Reporter: Jiří Holuša
> Assignee: Jiří Holuša
> Attachments: Snímek z 2016-01-29 11-37-21.png
>
>
> Page: Cache -> select some container -> list of caches
> Under certain circumstances, the cache cards are wrongly aligned, see the screenshot in attachments. I think it's because those two caches on the right don't have any icons below the cache type, making the box smaller.
> The solution would be to assign fixed height, since it can be predictable or add a "clearing" div after each row, I guess.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months