[JBoss JIRA] (ISPN-7391) Provide simple username/password/realm configuration attributes for the Hot Rod client
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-7391:
-------------------------------------
Summary: Provide simple username/password/realm configuration attributes for the Hot Rod client
Key: ISPN-7391
URL: https://issues.jboss.org/browse/ISPN-7391
Project: Infinispan
Issue Type: Enhancement
Components: Remote Protocols
Reporter: Tristan Tarrant
Fix For: 9.0.0.Final
Asking the user to specify a callback handler is overkill when most of the time he just needs username/password/realm. Allow these to be set easily by using an internal basic callbackhandler. This configuration would be mutually exclusive with an explicit callback handler
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[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 stopped 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: 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)
9 years, 2 months
[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)
9 years, 2 months
[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)
9 years, 2 months
[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)
9 years, 2 months
[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)
9 years, 2 months