January 2017 - infinispan-issues - Jboss List Archives

[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.... ] Ryan Emerson resolved ISPN-5941. -------------------------------- Fix Version/s: 9.0.0.Beta3 Resolution: Done > 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: 9.0.0.Beta3 > > > 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)

7 years, 8 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.... ] Ryan Emerson updated ISPN-5941: ------------------------------- Fix Version/s: (was: 8.2.0.Final) (was: 8.2.0.Beta1) > 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: 9.0.0.Beta3 > > > 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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7381) PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks'

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7381?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-7381: ----------------------------------------- [~pruivo] Sure > PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks' > -------------------------------------------------------------------------- > > Key: ISPN-7381 > URL: https://issues.jboss.org/browse/ISPN-7381 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 9.0.0.Beta1 > Reporter: Gustavo Fernandes > > This can be observed on {{AffinityTopologyChangeTest}}: > {noformat} > 09:49:44,566 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [82] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)09:49:44,794 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [111] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7381) PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks'

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7381?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-7381: ----------------------------------- [~gustavonalle] can you try: https://github.com/pruivo/infinispan/tree/t_7381 > PutKeyValueCommand fails with 'Timeout after 180 seconds waiting for acks' > -------------------------------------------------------------------------- > > Key: ISPN-7381 > URL: https://issues.jboss.org/browse/ISPN-7381 > Project: Infinispan > Issue Type: Bug > Components: Core, Embedded Querying > Affects Versions: 9.0.0.Beta1 > Reporter: Gustavo Fernandes > > This can be observed on {{AffinityTopologyChangeTest}}: > {noformat} > 09:49:44,566 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [82] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)09:49:44,794 ERROR (timeout-thread-AffinityTopologyChangeTest-NodeB-p11-t1) [InvocationContextInterceptor] ISPN000136: Error executing command PutKeyValueCommand, writing keys [111] > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 180 seconds waiting for acks > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:270) > at org.infinispan.util.concurrent.CommandAckCollector.access$200(CommandAckCollector.java:46) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:293) > at org.infinispan.util.concurrent.CommandAckCollector$Collector.call(CommandAckCollector.java:273) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7076) Cache clear doesn't work when passivation is enabled

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7076?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7076: -------------------------------- Status: Open (was: New) > Cache clear doesn't work when passivation is enabled > ---------------------------------------------------- > > Key: ISPN-7076 > URL: https://issues.jboss.org/browse/ISPN-7076 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Loaders and Stores > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Tristan Tarrant > Assignee: William Burns > Priority: Critical > > Hi, > I used the quick start https://github.com/jboss-developer/jboss-jdg-quickstarts/tree/jdg-6.6.x/h... to test a strange behaviour of Data Grid 6.6 used in library mode inside JBoss EAP 6.4.6. > The clear of the map doesn’t work if the passivation is enabled: the size is never be equal to 0 > If I set the passivation to false the clear works as I expected and the result of the size method of the map is 0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7076) Cache clear doesn't work when passivation is enabled

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7076?page=com.atlassian.jira.plugin.... ] Work on ISPN-7076 started by William Burns. ------------------------------------------- > Cache clear doesn't work when passivation is enabled > ---------------------------------------------------- > > Key: ISPN-7076 > URL: https://issues.jboss.org/browse/ISPN-7076 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Loaders and Stores > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Tristan Tarrant > Assignee: William Burns > Priority: Critical > > Hi, > I used the quick start https://github.com/jboss-developer/jboss-jdg-quickstarts/tree/jdg-6.6.x/h... to test a strange behaviour of Data Grid 6.6 used in library mode inside JBoss EAP 6.4.6. > The clear of the map doesn’t work if the passivation is enabled: the size is never be equal to 0 > If I set the passivation to false the clear works as I expected and the result of the size method of the map is 0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-7327?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-7327: --------------------------------- Description: Tracking JIRA for issues to be backported to 8.2.x for 8.2.7.Final. (was: Tracking JIRA for issues to be backported to 8.2.x for 8.2.6.Final.) > Backports for 8.2.7.Final > ------------------------- > > Key: ISPN-7327 > URL: https://issues.jboss.org/browse/ISPN-7327 > Project: Infinispan > Issue Type: Task > Affects Versions: 8.2.5.Final, 8.2.6.Final > Reporter: Paul Ferraro > Fix For: 8.2.7.Final > > > Tracking JIRA for issues to be backported to 8.2.x for 8.2.7.Final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-7327?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-7327: --------------------------------- Summary: Backports for 8.2.7.Final (was: Backports for 8.2.6.Final) > Backports for 8.2.7.Final > ------------------------- > > Key: ISPN-7327 > URL: https://issues.jboss.org/browse/ISPN-7327 > Project: Infinispan > Issue Type: Task > Affects Versions: 8.2.5.Final, 8.2.6.Final > Reporter: Paul Ferraro > Fix For: 8.2.7.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)

7 years, 8 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-7327?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-7327: --------------------------------- Affects Version/s: 8.2.6.Final > Backports for 8.2.7.Final > ------------------------- > > Key: ISPN-7327 > URL: https://issues.jboss.org/browse/ISPN-7327 > Project: Infinispan > Issue Type: Task > Affects Versions: 8.2.5.Final, 8.2.6.Final > Reporter: Paul Ferraro > Fix For: 8.2.7.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)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6963) Implement a Ceph store to be used as a CacheLoader

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6963?page=com.atlassian.jira.plugin.... ] Vojtech Juranek commented on ISPN-6963: --------------------------------------- Initial implementation in https://github.com/vjuranek/infinispan-cachestore-ceph > Implement a Ceph store to be used as a CacheLoader > -------------------------------------------------- > > Key: ISPN-6963 > URL: https://issues.jboss.org/browse/ISPN-6963 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Priority: Minor > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017