January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7331) Administration console - removing task before undeploying it should show an error

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-7331?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-7331: ------------------------------ Attachment: local-task.jar > Administration console - removing task before undeploying it should show an error > --------------------------------------------------------------------------------- > > Key: ISPN-7331 > URL: https://issues.jboss.org/browse/ISPN-7331 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Beta1 > Reporter: Jiří Holuša > Attachments: local-task.jar > > > Steps to reproduce: > Go to cache container -> Configuration -> Deployments -> upload some task (you can use the one in attachment) -> Deploy the task -> try clicking Remove > The task is correctly not removed, since it's not undeployed yet. However, there used to be a popup windows which showed, why the task could not be removed. I think it should be put back since it's much more user-friendly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7331) Administration console - removing task before undeploying it should show an error

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-7331: --------------------------------- Summary: Administration console - removing task before undeploying it should show an error Key: ISPN-7331 URL: https://issues.jboss.org/browse/ISPN-7331 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.0.0.Beta1 Reporter: Jiří Holuša Steps to reproduce: Go to cache container -> Configuration -> Deployments -> upload some task (you can use the one in attachment) -> Deploy the task -> try clicking Remove The task is correctly not removed, since it's not undeployed yet. However, there used to be a popup windows which showed, why the task could not be removed. I think it should be put back since it's much more user-friendly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7330) Administration console - cannot edit configuration twice without refresh

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-7330: --------------------------------- Summary: Administration console - cannot edit configuration twice without refresh Key: ISPN-7330 URL: https://issues.jboss.org/browse/ISPN-7330 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.0.0.Beta1 Reporter: Jiří Holuša Steps to reproduce: Go to cache configuration -> e.g. Locking tab -> edit some of the settings like "Acquire Timeout" -> Apply changes -> confirm everything. Now stay still on the page and edit the e.g. Isolation level -> Apply changes and you get an error: {code} {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:":{"Operation step-5":"WFLYCTL0212: Duplicate resource [\n (\"profile\" => \"clustered\"),\n (\"subsystem\" => \"datagrid-infinispan\"),\n (\"cache-container\" => \"clustered\"),\n (\"configurations\" => \"CONFIGURATIONS\"),\n (\"replicated-cache-configuration\" => \"replicatedCache\"),\n (\"eviction\" => \"EVICTION\")\n]"}} {code} I haven't clicked through the whole UI, but it seems that it's also in other tabs. Also I'm not sure if it's related only in changes in SELECTs or also in INPUTs, sometimes I was very confused what's going on. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7328) Administration console - cache statuses in cache container page behave randomly

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-7328?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-7328: ------------------------------ Description: Steps to reproduce: create more caches (in my case at least ~20), go to cache container and try to refresh the page several times. It should sometimes appear that some of the cache has yellow warning status, see attached screenshot. This occurs very randomly and only with more caches (and probably more servers). IMHO there is some kind of timeout issue that the console fails to retrieve statuses from all caches in time. I think the best solution would be to, when waiting for retrieving of the cache status, have instead of "warning" icon some kind of spinner which would basically signal "I haven't got the status yet". This would also solve a bit of user-unfriendliness, which is when you go to cache container, initially all the statuses are "warning" and then they change to "OK". This moment can time quite some time when there are more caches and can confuse users quite a bit. was: Steps to reproduce: create more caches (in my case at least ~20), go to cache container and try to refresh the page several times. It should sometimes appear that some of the cache has yellow warning status, see attached screenshot. This occurs very randomly and only with more caches (and probably more servers). IMHO there is some kind of timeout issue that the console fails to retrieve statuses from all caches in time. > Administration console - cache statuses in cache container page behave randomly > ------------------------------------------------------------------------------- > > Key: ISPN-7328 > URL: https://issues.jboss.org/browse/ISPN-7328 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Beta1 > Reporter: Jiří Holuša > Attachments: screenshot1.png > > > Steps to reproduce: create more caches (in my case at least ~20), go to cache container and try to refresh the page several times. It should sometimes appear that some of the cache has yellow warning status, see attached screenshot. > This occurs very randomly and only with more caches (and probably more servers). IMHO there is some kind of timeout issue that the console fails to retrieve statuses from all caches in time. > I think the best solution would be to, when waiting for retrieving of the cache status, have instead of "warning" icon some kind of spinner which would basically signal "I haven't got the status yet". This would also solve a bit of user-unfriendliness, which is when you go to cache container, initially all the statuses are "warning" and then they change to "OK". This moment can time quite some time when there are more caches and can confuse users quite a bit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7328) Administration console - cache statuses in cache container page behave randomly

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-7328?page=com.atlassian.jira.plugin.... ] Jiří Holuša reassigned ISPN-7328: --------------------------------- Assignee: Vladimir Blagojevic > Administration console - cache statuses in cache container page behave randomly > ------------------------------------------------------------------------------- > > Key: ISPN-7328 > URL: https://issues.jboss.org/browse/ISPN-7328 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Beta1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Attachments: screenshot1.png > > > Steps to reproduce: create more caches (in my case at least ~20), go to cache container and try to refresh the page several times. It should sometimes appear that some of the cache has yellow warning status, see attached screenshot. > This occurs very randomly and only with more caches (and probably more servers). IMHO there is some kind of timeout issue that the console fails to retrieve statuses from all caches in time. > I think the best solution would be to, when waiting for retrieving of the cache status, have instead of "warning" icon some kind of spinner which would basically signal "I haven't got the status yet". This would also solve a bit of user-unfriendliness, which is when you go to cache container, initially all the statuses are "warning" and then they change to "OK". This moment can time quite some time when there are more caches and can confuse users quite a bit. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7329) Administration console - cannot edit eviction

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-7329?page=com.atlassian.jira.plugin.... ] Jiří Holuša reassigned ISPN-7329: --------------------------------- Assignee: Vladimir Blagojevic > Administration console - cannot edit eviction > --------------------------------------------- > > Key: ISPN-7329 > URL: https://issues.jboss.org/browse/ISPN-7329 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.Beta1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Attachments: screenshot.png > > > Steps to reproduce: go to cache configuration -> click Eviction tab -> it's empty, see the attached screenshot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7329) Administration console - cannot edit eviction

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-7329: --------------------------------- Summary: Administration console - cannot edit eviction Key: ISPN-7329 URL: https://issues.jboss.org/browse/ISPN-7329 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.0.0.Beta1 Reporter: Jiří Holuša Attachments: screenshot.png Steps to reproduce: go to cache configuration -> click Eviction tab -> it's empty, see the attached screenshot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7328) Administration console - cache statuses in cache container page behave randomly

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-7328: --------------------------------- Summary: Administration console - cache statuses in cache container page behave randomly Key: ISPN-7328 URL: https://issues.jboss.org/browse/ISPN-7328 Project: Infinispan Issue Type: Bug Components: Console Affects Versions: 9.0.0.Beta1 Reporter: Jiří Holuša Attachments: screenshot1.png Steps to reproduce: create more caches (in my case at least ~20), go to cache container and try to refresh the page several times. It should sometimes appear that some of the cache has yellow warning status, see attached screenshot. This occurs very randomly and only with more caches (and probably more servers). IMHO there is some kind of timeout issue that the console fails to retrieve statuses from all caches in time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7327) Backports for 8.2.6.Final

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-7327: ---------------------------------- Summary: Backports for 8.2.6.Final Key: ISPN-7327 URL: https://issues.jboss.org/browse/ISPN-7327 Project: Infinispan Issue Type: Task Affects Versions: 8.2.5.Final Reporter: Paul Ferraro Fix For: 8.2.6.Final Tracking JIRA for issues to be backported to 8.2.x for 8.2.6.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (HRJS-31) Old connections not disconnected when switching sites

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-31?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-31: --------------------------------- Status: Open (was: New) > Old connections not disconnected when switching sites > ----------------------------------------------------- > > Key: HRJS-31 > URL: https://issues.jboss.org/browse/HRJS-31 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.4.0 > > > When a site change happens in the client, old connections are left lingering and they're not disconnected. Before installing any new routers for any sites, irrespective of whether the switch was manual or a as a result of a failover, old connections need to be disconnected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017