[JBoss JIRA] (HRJS-18) Local server iterator test fails and hangs randomly with NoSuchElementException
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-18?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño reassigned HRJS-18:
------------------------------------
Assignee: Galder Zamarreño
> Local server iterator test fails and hangs randomly with NoSuchElementException
> -------------------------------------------------------------------------------
>
> Key: HRJS-18
> URL: https://issues.jboss.org/browse/HRJS-18
> 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
>
> Attachments: server.log, tmp-tests.log
>
>
> Apart from the server returning {{NoSuchElementException}}, this is causing confusion in the client which results in the testsuite hanging completely.
> Here are snippets from client and server logs:
> {code}
> [2016-06-01 17:57:36.210] [DEBUG] client - Invoke putAll(msgId=323,pairs=[{"key":"local-it1","value":"v1","done":false},{"key":"local-it2","value":"v2","done":false},{"key":"local-it3","value":"v3","done":false}],opts=undefined)
> [2016-06-01 17:57:36.210] [TRACE] encoder - Encode operation with topology id 0
> [2016-06-01 17:57:36.210] [TRACE] transport - Write buffer(msgId=323) to 127.0.0.1:11222: A0C302192D000003007703096C6F63616C2D697431027631096C6F63616C2D697432027632096C6F63616C2D697433027633
> [2016-06-01 17:57:36.214] [TRACE] decoder - Read header(msgId=323): opCode=46, status=0, hasNewTopology=0
> [2016-06-01 17:57:36.215] [TRACE] decoder - Call decode for request(msgId=323)
> [2016-06-01 17:57:36.215] [TRACE] connection - After decoding request(msgId=323), buffer size is 6, and offset 6
> [2016-06-01 17:57:36.215] [TRACE] connection - Complete success for request(msgId=323) with undefined
> [2016-06-01 17:57:36.215] [DEBUG] client - Invoke iterator(msgId=324,batchSize=1,opts=undefined)
> [2016-06-01 17:57:36.215] [TRACE] encoder - Encode operation with topology id 0
> [2016-06-01 17:57:36.215] [TRACE] transport - Write buffer(msgId=324) to 127.0.0.1:11222: A0C40219310000030001010100
> [2016-06-01 17:57:36.230] [TRACE] decoder - Read header(msgId=324): opCode=50, status=0, hasNewTopology=0
> [2016-06-01 17:57:36.230] [TRACE] decoder - Call decode for request(msgId=324)
> [2016-06-01 17:57:36.230] [TRACE] connection - After decoding request(msgId=324), buffer size is 43, and offset 43
> [2016-06-01 17:57:36.230] [TRACE] connection - Complete success for request(msgId=324) with {"iterId":"28cab848-73ac-47c5-ad68-f518b89c5ba4","conn":{}}
> [2016-06-01 17:57:36.230] [TRACE] client - Invoke iterator.next(msgId=325,iteratorId=28cab848-73ac-47c5-ad68-f518b89c5ba4) on 127.0.0.1:11222
> [2016-06-01 17:57:36.230] [TRACE] encoder - Encode operation with topology id 0
> [2016-06-01 17:57:36.231] [TRACE] transport - Write buffer(msgId=325) to 127.0.0.1:11222: A0C5021933000003002432386361623834382D373361632D343763352D616436382D663531386238396335626134
> [2016-06-01 17:57:36.231] [TRACE] client - Invoke iterator.next(msgId=326,iteratorId=28cab848-73ac-47c5-ad68-f518b89c5ba4) on 127.0.0.1:11222
> [2016-06-01 17:57:36.231] [TRACE] encoder - Encode operation with topology id 0
> [2016-06-01 17:57:36.231] [TRACE] transport - Write buffer(msgId=326) to 127.0.0.1:11222: A0C6021933000003002432386361623834382D373361632D343763352D616436382D663531386238396335626134
> [2016-06-01 17:57:36.231] [TRACE] client - Invoke iterator.next(msgId=327,iteratorId=28cab848-73ac-47c5-ad68-f518b89c5ba4) on 127.0.0.1:11222
> [2016-06-01 17:57:36.231] [TRACE] encoder - Encode operation with topology id 0
> [2016-06-01 17:57:36.231] [TRACE] transport - Write buffer(msgId=327) to 127.0.0.1:11222: A0C7021933000003002432386361623834382D373361632D343763352D616436382D663531386238396335626134
> [2016-06-01 17:57:36.244] [TRACE] decoder - Read header(msgId=327): opCode=80, status=133, hasNewTopology=0
> [2016-06-01 17:57:36.244] [ERROR] decoder - Error decoding body of request(msgId=327): java.util.NoSuchElementException
> [2016-06-01 17:57:36.244] [TRACE] connection - After decoding request(msgId=327), buffer size is 39, and offset 39
> [2016-06-01 17:57:36.244] [TRACE] connection - Complete failure for request(msgId=327) with java.util.NoSuchElementException
> [2016-06-01 17:57:36.249] [TRACE] decoder - Read header(msgId=327): opCode=52, status=0, hasNewTopology=0
> {code}
> {code}
> 2016-06-01 17:57:36,216 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decoded header HotRodHeader{op=IterationStartRequest, version=25, messageId=324, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> 2016-06-01 17:57:36,222 TRACE [org.infinispan.interceptors.impl.InvocationContextInterceptor] (HotRodServerHandler-6-115) Invoked with command EntrySetCommand{cache=default} and InvocationContext [org.infinispan.context.impl.NonTxInvocationContext@7bc2d6d3]
> 2016-06-01 17:57:36,222 TRACE [org.infinispan.interceptors.impl.CallInterceptor] (HotRodServerHandler-6-115) Executing command: EntrySetCommand{cache=default}.
> 2016-06-01 17:57:36,229 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-6-115) Write response IterationStartResponse{version=25, messageId=324, cacheName=, operation=IterationStartResponse, status=Success, iterationId=28cab848-73ac-47c5-ad68-f518b89c5ba4}
> 2016-06-01 17:57:36,229 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-8-2) Encode msg IterationStartResponse{version=25, messageId=324, cacheName=, operation=IterationStartResponse, status=Success, iterationId=28cab848-73ac-47c5-ad68-f518b89c5ba4}
> 2016-06-01 17:57:36,229 TRACE [org.infinispan.server.hotrod.Encoder2x$] (HotRodServerWorker-8-2) Write topology response header with no change
> 2016-06-01 17:57:36,229 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-8-2) Write buffer contents A1C4023200002432386361623834382D373361632D343763352D616436382D663531386238396335626134 to channel [id: 0xd8959d2b, L:/127.0.0.1:11222 - R:/127.0.0.1:52367]
> 2016-06-01 17:57:36,231 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decode using instance @54abd903
> 2016-06-01 17:57:36,231 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=325, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> 2016-06-01 17:57:36,231 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decode using instance @54abd903
> 2016-06-01 17:57:36,231 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=326, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> 2016-06-01 17:57:36,231 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decode using instance @54abd903
> 2016-06-01 17:57:36,231 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-8-2) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=327, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> 2016-06-01 17:57:36,239 DEBUG [org.infinispan.server.hotrod.HotRodExceptionHandler] (HotRodServerWorker-8-2) Exception caught: java.util.NoSuchElementException
> at org.infinispan.stream.impl.RemovableIterator.next(RemovableIterator.java:49)
> at scala.collection.convert.Wrappers$JIteratorWrapper.next(Wrappers.scala:43)
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager$$anonfun$next$1$$anonfun$6.apply(IterationManager.scala:142)
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager$$anonfun$next$1$$anonfun$6.apply(IterationManager.scala:142)
> at scala.collection.TraversableLike$WithFilter$$anonfun$map$2.apply(TraversableLike.scala:728)
> at scala.collection.immutable.Range.foreach(Range.scala:166)
> at scala.collection.TraversableLike$WithFilter.map(TraversableLike.scala:727)
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager$$anonfun$next$1.apply(IterationManager.scala:142)
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager$$anonfun$next$1.apply(IterationManager.scala:138)
> at scala.Option.map(Option.scala:146)
> at org.infinispan.server.hotrod.iteration.DefaultIterationManager.next(IterationManager.scala:138)
> at org.infinispan.server.hotrod.ContextHandler.realRead(ContextHandler.java:182)
> at org.infinispan.server.hotrod.ContextHandler.lambda$channelRead0$1(ContextHandler.java:56)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:145)
> at java.lang.Thread.run(Thread.java:745)
> 2016-06-01 17:57:36,244 TRACE [org.infinispan.server.hotrod.HotRodEncoder] (HotRodServerWorker-8-2) Encode msg ErrorResponse{version=25, messageId=327, operation=ErrorResponse, status=ServerError, msg=java.util.NoSuchElementException}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-33) Cluster tests randomly fail iteration
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-33?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño closed HRJS-33.
--------------------------------
Fix Version/s: HRJS-18
Assignee: Galder Zamarreño
Resolution: Duplicate Issue
> Cluster tests randomly fail iteration
> -------------------------------------
>
> Key: HRJS-33
> URL: https://issues.jboss.org/browse/HRJS-33
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: HRJS-18
>
> Attachments: server-trace-logs.tgz
>
>
> Very sheldon the cluster spec iteration tests fail with:
> {code}
> Failures:
> 1) Infinispan cluster client can iterate over entries in a cluster
> Message:
> java.util.NoSuchElementException
> Stacktrace:
> undefined
> 2) Infinispan cluster client can remove listener in cluster
> Message:
> timeout: timed out after 5000 msec waiting for spec to complete
> Stacktrace:
> undefined
> 3) Infinispan cluster client can execute a script remotely to store and retrieve data in cluster mode
> Message:
> Expected 'cluster-typed-key' to be 'listen-distinct-1'.
> Stacktrace:
> Error: Expected 'cluster-typed-key' to be 'listen-distinct-1'.
> at EventEmitter.<anonymous> (/Users/g/0/infinispan/js-client/spec/utils/testing.js:317:26)
> at EventEmitter.emit (events.js:106:17)
> at emitKeyVersion (/Users/g/0/infinispan/js-client/lib/protocols.js:411:29)
> at /Users/g/0/infinispan/js-client/lib/protocols.js:399:18
> at Function.<anonymous> (/Users/g/0/infinispan/js-client/lib/functional.js:185:16)
> at /Users/g/0/infinispan/js-client/lib/functional.js:173:19
> at ListenersMixin.decodeEvent (/Users/g/0/infinispan/js-client/lib/protocols.js:475:18)
> at Socket.onData (/Users/g/0/infinispan/js-client/lib/io.js:103:38)
> 4) Infinispan cluster client can execute a script remotely to store and retrieve data in cluster mode
> Message:
> timeout: timed out after 5000 msec waiting for spec to complete
> Stacktrace:
> undefined
> 5) Infinispan cluster client can execute a script remotely to store and retrieve data in distributed mode
> Message:
> Expected 'dist-cluster-typed-key' to be 'listen-distinct-1'.
> Stacktrace:
> Error: Expected 'dist-cluster-typed-key' to be 'listen-distinct-1'.
> at EventEmitter.<anonymous> (/Users/g/0/infinispan/js-client/spec/utils/testing.js:317:26)
> at EventEmitter.emit (events.js:106:17)
> at emitKeyVersion (/Users/g/0/infinispan/js-client/lib/protocols.js:411:29)
> at /Users/g/0/infinispan/js-client/lib/protocols.js:399:18
> at Function.<anonymous> (/Users/g/0/infinispan/js-client/lib/functional.js:185:16)
> at /Users/g/0/infinispan/js-client/lib/functional.js:173:19
> at ListenersMixin.decodeEvent (/Users/g/0/infinispan/js-client/lib/protocols.js:475:18)
> at Socket.onData (/Users/g/0/infinispan/js-client/lib/io.js:103:38)
> Finished in 12.721 seconds
> 10 tests, 26 assertions, 5 failures, 0 skipped
> {code}
> See attached TRACE logs from server (unfortunately no client logs)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (ISPN-5941) Ensure testability of management console
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-5941?page=com.atlassian.jira.plugin.... ]
Alan Field reopened ISPN-5941:
------------------------------
I am reopening this issue after discussions with the QE team. There are many UI elements that do not have IDs which causes unneeded instability in the console test suite
> 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: Vladimir Blagojevic
> 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)
7 years, 4 months
[JBoss JIRA] (HRJS-25) Test pkill command might be killing itself
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-25?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño resolved HRJS-25.
----------------------------------
Fix Version/s: (was: 0.4.0)
Resolution: Rejected
Solved independently by HRJS-30 where no pkill command is needed any more.
> Test pkill command might be killing itself
> ------------------------------------------
>
> Key: HRJS-25
> URL: https://issues.jboss.org/browse/HRJS-25
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> In some environments (e.g. ubuntu), failover and xsite tests fail with errors like this:
> {code}
> 1) Infinispan cluster client can failover when nodes crash
> Message:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> Stacktrace:
> Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
> at ChildProcess.exithandler (child_process.js:213:12)
> at emitTwo (events.js:87:13)
> at ChildProcess.emit (events.js:172:7)
> at maybeClose (internal/child_process.js:854:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
> {code}
> After adding more info the error, we've found that the error contains:
> {code}
> exec error (JS): {"killed":false,"code":null,"signal":"SIGKILL","cmd":"/bin/sh -c pkill -9 -f '.*java.*node4 .*'"}
> {code}
> The node.js documentation says:
> {code}
> If the process terminated normally, code is the final exit code of
> the process, otherwise null. If the process terminated due to
> receipt of a signal, signal is the string name of the signal,
> otherwise null.
> {code}
> So, it might imply that the {{pkill}} command is killing itself...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-30) Move testsuite server orchestration to a domain
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-30?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-30:
---------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/js-client/pull/12
> Move testsuite server orchestration to a domain
> -----------------------------------------------
>
> Key: HRJS-30
> URL: https://issues.jboss.org/browse/HRJS-30
> Project: Infinispan Javascript client
> Issue Type: Enhancement
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 0.4.0
>
>
> As more tests have been added to the Infinispan JS testsuite, the existing simple server orchestration script/environment are turning out to be a bit painful to deal with.
> On one hand, Haskell's {{stack}} can be sometimes difficult to install in some envs, e.g. Ubuntu. I've also seen issues with Turtle library used in Haskell and copying contents inside symbolic links in Red Hat Linux.
> On top of that, as security and cross-site tests were added, more configurations were added and more servers need to be added, making it track the configs a bit more confusing.
> Finally, the methods used to start/stop servers in self-contained tests, e.g. xsite and cluster failover, a little bit clunky.
> So, with this in mind, we thought of using more suitable orchestration techniques for Infinispan servers. We considered docker compose and kubernetes, but since the servers just simply need to run in a single machine and there's not a huge need to have clean environments, we decided to use a single Infinispan server domain to orchestrate all servers.
> The advantages of domain is that is easy to start all servers with the right configuration very quickly, and start/stop servers from tests is very easy and quick compared with current approach. On top of that, having domain based orchestration will make it easy to port over the servers, their configs and script over to testsuites of other langs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-33) Cluster tests randomly fail iteration
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-33?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-33:
---------------------------------
Attachment: server-trace-logs.tgz
> Cluster tests randomly fail iteration
> -------------------------------------
>
> Key: HRJS-33
> URL: https://issues.jboss.org/browse/HRJS-33
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Attachments: server-trace-logs.tgz
>
>
> Very sheldon the cluster spec iteration tests fail with:
> {code}
> Failures:
> 1) Infinispan cluster client can iterate over entries in a cluster
> Message:
> java.util.NoSuchElementException
> Stacktrace:
> undefined
> 2) Infinispan cluster client can remove listener in cluster
> Message:
> timeout: timed out after 5000 msec waiting for spec to complete
> Stacktrace:
> undefined
> 3) Infinispan cluster client can execute a script remotely to store and retrieve data in cluster mode
> Message:
> Expected 'cluster-typed-key' to be 'listen-distinct-1'.
> Stacktrace:
> Error: Expected 'cluster-typed-key' to be 'listen-distinct-1'.
> at EventEmitter.<anonymous> (/Users/g/0/infinispan/js-client/spec/utils/testing.js:317:26)
> at EventEmitter.emit (events.js:106:17)
> at emitKeyVersion (/Users/g/0/infinispan/js-client/lib/protocols.js:411:29)
> at /Users/g/0/infinispan/js-client/lib/protocols.js:399:18
> at Function.<anonymous> (/Users/g/0/infinispan/js-client/lib/functional.js:185:16)
> at /Users/g/0/infinispan/js-client/lib/functional.js:173:19
> at ListenersMixin.decodeEvent (/Users/g/0/infinispan/js-client/lib/protocols.js:475:18)
> at Socket.onData (/Users/g/0/infinispan/js-client/lib/io.js:103:38)
> 4) Infinispan cluster client can execute a script remotely to store and retrieve data in cluster mode
> Message:
> timeout: timed out after 5000 msec waiting for spec to complete
> Stacktrace:
> undefined
> 5) Infinispan cluster client can execute a script remotely to store and retrieve data in distributed mode
> Message:
> Expected 'dist-cluster-typed-key' to be 'listen-distinct-1'.
> Stacktrace:
> Error: Expected 'dist-cluster-typed-key' to be 'listen-distinct-1'.
> at EventEmitter.<anonymous> (/Users/g/0/infinispan/js-client/spec/utils/testing.js:317:26)
> at EventEmitter.emit (events.js:106:17)
> at emitKeyVersion (/Users/g/0/infinispan/js-client/lib/protocols.js:411:29)
> at /Users/g/0/infinispan/js-client/lib/protocols.js:399:18
> at Function.<anonymous> (/Users/g/0/infinispan/js-client/lib/functional.js:185:16)
> at /Users/g/0/infinispan/js-client/lib/functional.js:173:19
> at ListenersMixin.decodeEvent (/Users/g/0/infinispan/js-client/lib/protocols.js:475:18)
> at Socket.onData (/Users/g/0/infinispan/js-client/lib/io.js:103:38)
> Finished in 12.721 seconds
> 10 tests, 26 assertions, 5 failures, 0 skipped
> {code}
> See attached TRACE logs from server (unfortunately no client logs)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (HRJS-33) Cluster tests randomly fail iteration
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-33?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño updated HRJS-33:
---------------------------------
Affects Version/s: 0.3.0
> Cluster tests randomly fail iteration
> -------------------------------------
>
> Key: HRJS-33
> URL: https://issues.jboss.org/browse/HRJS-33
> Project: Infinispan Javascript client
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Galder Zamarreño
> Attachments: server-trace-logs.tgz
>
>
> Very sheldon the cluster spec iteration tests fail with:
> {code}
> Failures:
> 1) Infinispan cluster client can iterate over entries in a cluster
> Message:
> java.util.NoSuchElementException
> Stacktrace:
> undefined
> 2) Infinispan cluster client can remove listener in cluster
> Message:
> timeout: timed out after 5000 msec waiting for spec to complete
> Stacktrace:
> undefined
> 3) Infinispan cluster client can execute a script remotely to store and retrieve data in cluster mode
> Message:
> Expected 'cluster-typed-key' to be 'listen-distinct-1'.
> Stacktrace:
> Error: Expected 'cluster-typed-key' to be 'listen-distinct-1'.
> at EventEmitter.<anonymous> (/Users/g/0/infinispan/js-client/spec/utils/testing.js:317:26)
> at EventEmitter.emit (events.js:106:17)
> at emitKeyVersion (/Users/g/0/infinispan/js-client/lib/protocols.js:411:29)
> at /Users/g/0/infinispan/js-client/lib/protocols.js:399:18
> at Function.<anonymous> (/Users/g/0/infinispan/js-client/lib/functional.js:185:16)
> at /Users/g/0/infinispan/js-client/lib/functional.js:173:19
> at ListenersMixin.decodeEvent (/Users/g/0/infinispan/js-client/lib/protocols.js:475:18)
> at Socket.onData (/Users/g/0/infinispan/js-client/lib/io.js:103:38)
> 4) Infinispan cluster client can execute a script remotely to store and retrieve data in cluster mode
> Message:
> timeout: timed out after 5000 msec waiting for spec to complete
> Stacktrace:
> undefined
> 5) Infinispan cluster client can execute a script remotely to store and retrieve data in distributed mode
> Message:
> Expected 'dist-cluster-typed-key' to be 'listen-distinct-1'.
> Stacktrace:
> Error: Expected 'dist-cluster-typed-key' to be 'listen-distinct-1'.
> at EventEmitter.<anonymous> (/Users/g/0/infinispan/js-client/spec/utils/testing.js:317:26)
> at EventEmitter.emit (events.js:106:17)
> at emitKeyVersion (/Users/g/0/infinispan/js-client/lib/protocols.js:411:29)
> at /Users/g/0/infinispan/js-client/lib/protocols.js:399:18
> at Function.<anonymous> (/Users/g/0/infinispan/js-client/lib/functional.js:185:16)
> at /Users/g/0/infinispan/js-client/lib/functional.js:173:19
> at ListenersMixin.decodeEvent (/Users/g/0/infinispan/js-client/lib/protocols.js:475:18)
> at Socket.onData (/Users/g/0/infinispan/js-client/lib/io.js:103:38)
> Finished in 12.721 seconds
> 10 tests, 26 assertions, 5 failures, 0 skipped
> {code}
> See attached TRACE logs from server (unfortunately no client logs)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months