April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6544) Management console should not be accessible in standalone mode

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6544?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6544: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Management console should not be accessible in standalone mode > -------------------------------------------------------------- > > Key: ISPN-6544 > URL: https://issues.jboss.org/browse/ISPN-6544 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > Attachments: Screenshot-standaloneMode.png > > > Management console is supported only in domain mode, but user can still log into console in standalone mode (no values are displayed, only skeleton of the console - please see the screenshot) > I believe Management Console should display a warning, saying that it's only supported in domain mode. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6298: ------------------------------------------- Thanks [~jholusa] Updated PR and closing this issue. > 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 > Fix For: 9.0.0.Alpha2 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6120) Management console - there should be a warning about possible data loss when stopping the cluster

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6120?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6120: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Management console - there should be a warning about possible data loss when stopping the cluster > ------------------------------------------------------------------------------------------------- > > Key: ISPN-6120 > URL: https://issues.jboss.org/browse/ISPN-6120 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > > Clusters tab -> cluster -> actions -> stop > When stopping cluster/node, pop up should show warning, saying that caches without configured cache store will loose data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6298: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/78 > 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 > Fix For: 9.0.0.Alpha2 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6298) Network partition detection not working in mgmt console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6298?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6298: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > 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 > Fix For: 9.0.0.Alpha2 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6540) Management console doesn't display cache containers correctly if there are two containers with the same name

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6540?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6540: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Alpha2 Resolution: Done > Management console doesn't display cache containers correctly if there are two containers with the same name > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-6540 > URL: https://issues.jboss.org/browse/ISPN-6540 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha2 > > Attachments: configs.zip, config_with_remoteSite.zip, Screenshot-containersWithSameName.png, Screenshot-detalPageForBothContainers.png > > > When we have two containers with the same name on different clusters some values are displayed correctly - #caches, name, clustering-info, but some are not - endpoints, sites. > Additionally, clicking on either of containers display the same information, even though containers are configured differently. > Please see the screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6575: -------------------------------- Status: Open (was: New) > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-6575: ----------------------------------- Assignee: William Burns > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6575: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4294 > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6575) SkipOperation uses limit instead of skip

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-6575?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-6575: -------------------------------- Fix Version/s: 9.0.0.Alpha2 8.2.2.Final > SkipOperation uses limit instead of skip > ---------------------------------------- > > Key: ISPN-6575 > URL: https://issues.jboss.org/browse/ISPN-6575 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.1.Final > Reporter: Henrik Johansson > Assignee: William Burns > Fix For: 9.0.0.Alpha2, 8.2.2.Final > > > The SkipOperation uses limit instead of skip. > https://github.com/infinispan/infinispan/pull/4288 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016