January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7369) PutMapCommand blocks in backup owner

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7369?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7369: ----------------------------------- Fix Version/s: 9.0.0.Beta2 > PutMapCommand blocks in backup owner > ------------------------------------ > > Key: ISPN-7369 > URL: https://issues.jboss.org/browse/ISPN-7369 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 9.0.0.Beta2 > > > When the TriangleOrderManager was introduced, the putAll() logic must had been updated as well. When numOnwer > 2, it causes the PutMapCommand to block forever (until timeout). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7370) Administration console - configuration of cache store is broken

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7370?page=com.atlassian.jira.plugin.... ] Roman Macor reassigned ISPN-7370: --------------------------------- Assignee: Vladimir Blagojevic > Administration console - configuration of cache store is broken > --------------------------------------------------------------- > > Key: ISPN-7370 > URL: https://issues.jboss.org/browse/ISPN-7370 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot from 2017-01-19.png > > > Click on cache container -> cache -> configuration -> Store -> Select store type e.g. Binary keyed JDBC store > Issues: > some property names are displayed like this: {{$ctrl.resolveFieldName()}} > ... links (for Write Behind for example) are not working > Please see the attached screenshot for details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7370) Administration console - configuration of cache store is broken

by Roman Macor (JIRA)

Roman Macor created ISPN-7370: --------------------------------- Summary: Administration console - configuration of cache store is broken Key: ISPN-7370 URL: https://issues.jboss.org/browse/ISPN-7370 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.Beta1 Reporter: Roman Macor Attachments: Screenshot from 2017-01-19.png Click on cache container -> cache -> configuration -> Store -> Select store type e.g. Binary keyed JDBC store Issues: some property names are displayed like this: {{$ctrl.resolveFieldName()}} ... links (for Write Behind for example) are not working Please see the attached screenshot for details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7369) PutMapCommand blocks in backup owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7369?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7369: ------------------------------ Status: Open (was: New) > PutMapCommand blocks in backup owner > ------------------------------------ > > Key: ISPN-7369 > URL: https://issues.jboss.org/browse/ISPN-7369 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > > When the TriangleOrderManager was introduced, the putAll() logic must had been updated as well. When numOnwer > 2, it causes the PutMapCommand to block forever (until timeout). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7369) PutMapCommand blocks in backup owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7369?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7369: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4772 > PutMapCommand blocks in backup owner > ------------------------------------ > > Key: ISPN-7369 > URL: https://issues.jboss.org/browse/ISPN-7369 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Critical > > When the TriangleOrderManager was introduced, the putAll() logic must had been updated as well. When numOnwer > 2, it causes the PutMapCommand to block forever (until timeout). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7369) PutMapCommand blocks in backup owner

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-7369: --------------------------------- Summary: PutMapCommand blocks in backup owner Key: ISPN-7369 URL: https://issues.jboss.org/browse/ISPN-7369 Project: Infinispan Issue Type: Bug Components: Core Reporter: Pedro Ruivo Assignee: Pedro Ruivo Priority: Critical When the TriangleOrderManager was introduced, the putAll() logic must had been updated as well. When numOnwer > 2, it causes the PutMapCommand to block forever (until timeout). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7345) Administration console - missing name of cluster in stop/start confirmation dialog

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7345?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7345. -------------------------------- Fix Version/s: 9.0.0.Beta2 Resolution: Done > Administration console - missing name of cluster in stop/start confirmation dialog > ---------------------------------------------------------------------------------- > > Key: ISPN-7345 > URL: https://issues.jboss.org/browse/ISPN-7345 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta2 > > > Click on clusters tab, click on cluster, actions -> start/stop > Confirmation pop up says: > Starting will start all previously running servers in this cluster. Start ? > It should say (it used to say): > Starting cluster_name will start all previously running servers in this cluster. Start cluster_name? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7328?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7328. -------------------------------- Fix Version/s: 9.0.0.Beta2 Resolution: Done > 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 > Priority: Minor > Fix For: 9.0.0.Beta2 > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5941) Ensure testability of management console

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-5941?page=com.atlassian.jira.plugin.... ] Work on ISPN-5941 started by Ryan Emerson. ------------------------------------------ > Ensure testability of management console > ---------------------------------------- > > Key: ISPN-5941 > URL: https://issues.jboss.org/browse/ISPN-5941 > Project: Infinispan > Issue Type: Task > Components: Console > Reporter: Jiří Holuša > Assignee: Ryan Emerson > Fix For: 8.2.0.Beta1, 8.2.0.Final > > > Since we're planning to test ISPN management console using Selenium (Selenide more specifically), we would appreciate taking more attention to giving ID's to page elements that would be helpful for testing. > Just an example, how it could simplify our test development as a motivation. Currently (ISPN 8.1.0.Alpha2), in the detail of cache container page with list of caches, the shortest way (even with Java 8) how to get (for testing purposes) names of caches, is: > {code} > List<String> caches = $$("#cache-cards > div").filterBy(attribute("ng-show", "cache.show")) > .stream().map(element -> element.find("a").text()).collect(Collectors.toList()); > {code} > The time to figure out this "query" was about 2 minutes (For the first time. I know, very subjective, but as an example) > Now suppose we would add class="cacheName" to <a> element of the corresponding cache card: > {code} > List<String> caches = $$("#cache-cards a.cacheName").stream().map(element -> element.text()).collect(Collectors.toList()); > {code} > Time to come up with such an "query" would be around 5 seconds :) > I tried to come up with some generic guidelines about where to put some id/class, feel free to add some: > * to every input/select field > * especially with checkboxes which are differentiated with <label> > * generally to <span> or any (text?) element which can change it's value, which is dependent on some state of the cache/server/... > Of course, you cannot be 100% successful with giving the id/class to every useful place, but every single place, which you select correctly, simplifies and speeds up the test development. Probably also a good idea to come up with some naming convention. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7367) CommandAckCollector Improvements

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7367?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7367: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4774 > CommandAckCollector Improvements > -------------------------------- > > Key: ISPN-7367 > URL: https://issues.jboss.org/browse/ISPN-7367 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > > Changes suggested: > * we can have a single {{CommandAckCollector}} per cache manager, since the {{CommandInvocationId}}s are unique. > * It doesn't need the complete {{CommandInvocationId}}. Only the {{long id}} is needed. > Result: > * Smaller payload in acks (no need to send the cache name neither the originator address) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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