March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10085) Hibernate51 and Hibernate53 tests are reporting the same test name

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10085?page=com.atlassian.jira.plugin... ] Diego Lovison reassigned ISPN-10085: ------------------------------------ Assignee: Diego Lovison > Hibernate51 and Hibernate53 tests are reporting the same test name > ------------------------------------------------------------------ > > Key: ISPN-10085 > URL: https://issues.jboss.org/browse/ISPN-10085 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Final, 9.4.11.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > > infinispan-hibernate-cache-v51 and infinispan-hibernate-cache-v53 are using the same tests. Let's say that v51 run first and the test has one error. when running with v53, the test result will be overwritten in the "Test Result" Jenkins plugin because they have the same name, arguments and class name. > the example is here > https://ci.infinispan.org/job/Infinispan/job/PR-6731/13/testReport/org.in... > is it a test for v51 or v53? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10085) Hibernate51 and Hibernate53 tests are reporting the same test name

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-10085?page=com.atlassian.jira.plugin... ] Diego Lovison updated ISPN-10085: --------------------------------- Status: Open (was: New) > Hibernate51 and Hibernate53 tests are reporting the same test name > ------------------------------------------------------------------ > > Key: ISPN-10085 > URL: https://issues.jboss.org/browse/ISPN-10085 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Final, 9.4.11.Final > Reporter: Diego Lovison > Priority: Critical > > infinispan-hibernate-cache-v51 and infinispan-hibernate-cache-v53 are using the same tests. Let's say that v51 run first and the test has one error. when running with v53, the test result will be overwritten in the "Test Result" Jenkins plugin because they have the same name, arguments and class name. > the example is here > https://ci.infinispan.org/job/Infinispan/job/PR-6731/13/testReport/org.in... > is it a test for v51 or v53? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10085) Hibernate51 and Hibernate53 tests are reporting the same test name

by Diego Lovison (Jira)

Diego Lovison created ISPN-10085: ------------------------------------ Summary: Hibernate51 and Hibernate53 tests are reporting the same test name Key: ISPN-10085 URL: https://issues.jboss.org/browse/ISPN-10085 Project: Infinispan Issue Type: Bug Affects Versions: 9.4.11.Final, 10.0.0.Final Reporter: Diego Lovison infinispan-hibernate-cache-v51 and infinispan-hibernate-cache-v53 are using the same tests. Let's say that v51 run first and the test has one error. when running with v53, the test result will be overwritten in the "Test Result" Jenkins plugin because they have the same name, arguments and class name. the example is here https://ci.infinispan.org/job/Infinispan/job/PR-6731/13/testReport/org.in... is it a test for v51 or v53? -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10077) ClientSocketReadTimeoutTest.testPutTimeout fails

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10077?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10077: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ClientSocketReadTimeoutTest.testPutTimeout fails > ------------------------------------------------ > > Key: ISPN-10077 > URL: https://issues.jboss.org/browse/ISPN-10077 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Environment: CI > https://ci.infinispan.org/job/Infinispan/job/9.4.x/158/testReport/org.inf... > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Error Message > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > Stacktrace > org.testng.TestException: > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at io.netty.channel.unix.Socket.finishConnect(..)(Unknown Source) > Caused by: io.netty.channel.unix.Errors$NativeConnectException: syscall:getsockopt(..) failed: Connection refused > ... 1 more > ... Removed 13 stack frames > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10073) Nested async operations with HotRod client hang

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10073?page=com.atlassian.jira.plugin... ] Tristan Tarrant commented on ISPN-10073: ---------------------------------------- [~dbosanac] what [~william.burns] is saying is that you should not be performing a blocking operation inside the callback. If you need to you should pass it to a separate thread > Nested async operations with HotRod client hang > ----------------------------------------------- > > Key: ISPN-10073 > URL: https://issues.jboss.org/browse/ISPN-10073 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.4.10.Final > Reporter: Dejan Bosanac > Assignee: William Burns > Priority: Major > > We noticed some issued with the HotRod client, when trying to use nested async calls. Originally, this was discovered in the context of Vert.x tests, but below you can find the smallest reproducer code that I could create (without any Vert.x dependencies). > {code:java} > //DefaultCacheManager cm = new DefaultCacheManager(); > //Cache<String, String> cache = cm.createCache("default", new ConfigurationBuilder().build()); > RemoteCacheManager cm = new RemoteCacheManager(); > RemoteCache<String, String> cache = cm.getCache("default"); > final CompletableFuture put = new CompletableFuture(); > cache.putIfAbsentAsync("A", "A").thenAccept(resultA -> { > final CompletableFuture nested = new CompletableFuture(); > cache.putIfAbsentAsync("B", "B").thenAccept(resultB -> { > nested.complete("B"); > }); > try { > nested.get(); > } catch (Exception e) { > e.printStackTrace(); > } > put.complete("B"); > }); > put.get(); > {code} > This would basically hang and the nested operation would never receive response. What I noticed in the original test is that response would become available after the framework timeout the test. > Everything works as expected with embedded cache. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10073) Nested async operations with HotRod client hang

by Dejan Bosanac (Jira)

[ https://issues.jboss.org/browse/ISPN-10073?page=com.atlassian.jira.plugin... ] Dejan Bosanac commented on ISPN-10073: -------------------------------------- Thanks [~william.burns]. Can you please let us know when you have a snapshot we can test? > Nested async operations with HotRod client hang > ----------------------------------------------- > > Key: ISPN-10073 > URL: https://issues.jboss.org/browse/ISPN-10073 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.4.10.Final > Reporter: Dejan Bosanac > Assignee: William Burns > Priority: Major > > We noticed some issued with the HotRod client, when trying to use nested async calls. Originally, this was discovered in the context of Vert.x tests, but below you can find the smallest reproducer code that I could create (without any Vert.x dependencies). > {code:java} > //DefaultCacheManager cm = new DefaultCacheManager(); > //Cache<String, String> cache = cm.createCache("default", new ConfigurationBuilder().build()); > RemoteCacheManager cm = new RemoteCacheManager(); > RemoteCache<String, String> cache = cm.getCache("default"); > final CompletableFuture put = new CompletableFuture(); > cache.putIfAbsentAsync("A", "A").thenAccept(resultA -> { > final CompletableFuture nested = new CompletableFuture(); > cache.putIfAbsentAsync("B", "B").thenAccept(resultB -> { > nested.complete("B"); > }); > try { > nested.get(); > } catch (Exception e) { > e.printStackTrace(); > } > put.complete("B"); > }); > put.get(); > {code} > This would basically hang and the nested operation would never receive response. What I noticed in the original test is that response would become available after the framework timeout the test. > Everything works as expected with embedded cache. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10074) DefaultSegmentedDataContainer executeTask() and iterator() include expired entries

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10074?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10074: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6799, https://github.com/infinispan/infinispan/pull/6800 > DefaultSegmentedDataContainer executeTask() and iterator() include expired entries > ---------------------------------------------------------------------------------- > > Key: ISPN-10074 > URL: https://issues.jboss.org/browse/ISPN-10074 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > The {{executeTask()}} javadoc doesn't mention expired entries, but {{iterator()}}'s says they shouldn't be included, and non-segmented containers do not include them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10077) ClientSocketReadTimeoutTest.testPutTimeout fails

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10077?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10077: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6804, https://github.com/infinispan/infinispan/pull/6805 > ClientSocketReadTimeoutTest.testPutTimeout fails > ------------------------------------------------ > > Key: ISPN-10077 > URL: https://issues.jboss.org/browse/ISPN-10077 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Environment: CI > https://ci.infinispan.org/job/Infinispan/job/9.4.x/158/testReport/org.inf... > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Error Message > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > Stacktrace > org.testng.TestException: > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at io.netty.channel.unix.Socket.finishConnect(..)(Unknown Source) > Caused by: io.netty.channel.unix.Errors$NativeConnectException: syscall:getsockopt(..) failed: Connection refused > ... 1 more > ... Removed 13 stack frames > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10077) ClientSocketReadTimeoutTest.testPutTimeout fails

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10077?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10077: ----------------------------------- Fix Version/s: 10.0.0.Beta4 9.4.12.Final > ClientSocketReadTimeoutTest.testPutTimeout fails > ------------------------------------------------ > > Key: ISPN-10077 > URL: https://issues.jboss.org/browse/ISPN-10077 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Environment: CI > https://ci.infinispan.org/job/Infinispan/job/9.4.x/158/testReport/org.inf... > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Error Message > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > Stacktrace > org.testng.TestException: > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at io.netty.channel.unix.Socket.finishConnect(..)(Unknown Source) > Caused by: io.netty.channel.unix.Errors$NativeConnectException: syscall:getsockopt(..) failed: Connection refused > ... 1 more > ... Removed 13 stack frames > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10077) ClientSocketReadTimeoutTest.testPutTimeout fails

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10077?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10077: ----------------------------------- Status: Open (was: New) > ClientSocketReadTimeoutTest.testPutTimeout fails > ------------------------------------------------ > > Key: ISPN-10077 > URL: https://issues.jboss.org/browse/ISPN-10077 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Environment: CI > https://ci.infinispan.org/job/Infinispan/job/9.4.x/158/testReport/org.inf... > Reporter: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Error Message > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > Stacktrace > org.testng.TestException: > Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 > at io.netty.channel.unix.Socket.finishConnect(..)(Unknown Source) > Caused by: io.netty.channel.unix.Errors$NativeConnectException: syscall:getsockopt(..) failed: Connection refused > ... 1 more > ... Removed 13 stack frames > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019