March 2019 - infinispan-issues - Jboss List Archives

[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 updated ISPN-10073: --------------------------------- Description: 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 = manager.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. was: 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 = manager.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} Everything works as expected with embedded cache. > 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 > 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 = manager.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)

7 years

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 updated ISPN-10073: --------------------------------- Description: 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 = manager.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} Everything works as expected with embedded cache. was: 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). {{ //DefaultCacheManager cm = new DefaultCacheManager(); //Cache<String, String> cache = cm.createCache("default", new ConfigurationBuilder().build()); RemoteCacheManager cm = new RemoteCacheManager(); RemoteCache<String, String> cache = manager.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();}} Everything works as expected with embedded cache. > 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 > 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 = manager.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} > Everything works as expected with embedded cache. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Dejan Bosanac (Jira)

Dejan Bosanac created ISPN-10073: ------------------------------------ Summary: 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 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). {{ //DefaultCacheManager cm = new DefaultCacheManager(); //Cache<String, String> cache = cm.createCache("default", new ConfigurationBuilder().build()); RemoteCacheManager cm = new RemoteCacheManager(); RemoteCache<String, String> cache = manager.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();}} Everything works as expected with embedded cache. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10066) Server remote store is missing server-name attribute

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10066?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10066. --------------------------------- Resolution: Done > Server remote store is missing server-name attribute > ---------------------------------------------------- > > Key: ISPN-10066 > URL: https://issues.jboss.org/browse/ISPN-10066 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.11.Final > > > When attempting to connect to a server with DIGEST authentication, the client needs to be able to specify the server name, otherwise the following error will happen "javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched URI: hotrod/null; expecting one of: hotrod/myserver" -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10072?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10072: -------------------------------- Status: Open (was: New) > Core module should export reactive-streams for store implementations > -------------------------------------------------------------------- > > Key: ISPN-10072 > URL: https://issues.jboss.org/browse/ISPN-10072 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta3 > > > As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10072?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10072: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6787 > Core module should export reactive-streams for store implementations > -------------------------------------------------------------------- > > Key: ISPN-10072 > URL: https://issues.jboss.org/browse/ISPN-10072 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta3 > > > As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10072: ----------------------------------- Summary: Core module should export reactive-streams for store implementations Key: ISPN-10072 URL: https://issues.jboss.org/browse/ISPN-10072 Project: Infinispan Issue Type: Enhancement Components: Server, WildFly modules Affects Versions: 10.0.0.Beta2 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Beta3 As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9306) Unguarded lazy initialization of SQL statements in JDBC CacheStore

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9306?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9306: ------------------------------- Fix Version/s: 10.0.0.Beta3 > Unguarded lazy initialization of SQL statements in JDBC CacheStore > ------------------------------------------------------------------ > > Key: ISPN-9306 > URL: https://issues.jboss.org/browse/ISPN-9306 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.3.0.CR1 > Reporter: Sanne Grinovero > Assignee: Diego Lovison > Priority: Major > Fix For: 10.0.0.Beta3 > > > Several fields in {{org.infinispan.persistence.jdbc.table.management.AbstractTableManager}} are lazily initialized by its child implementations, yet without any barrier. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9306) Unguarded lazy initialization of SQL statements in JDBC CacheStore

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9306?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-9306. -------------------------------- Resolution: Done > Unguarded lazy initialization of SQL statements in JDBC CacheStore > ------------------------------------------------------------------ > > Key: ISPN-9306 > URL: https://issues.jboss.org/browse/ISPN-9306 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.3.0.CR1 > Reporter: Sanne Grinovero > Assignee: Diego Lovison > Priority: Major > Fix For: 10.0.0.Beta3 > > > Several fields in {{org.infinispan.persistence.jdbc.table.management.AbstractTableManager}} are lazily initialized by its child implementations, yet without any barrier. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10055) Checkstyle 8.18

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10055?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10055. --------------------------------- Resolution: Done > Checkstyle 8.18 > --------------- > > Key: ISPN-10055 > URL: https://issues.jboss.org/browse/ISPN-10055 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Affects Versions: 10.0.0.Beta2, 9.4.9.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.11.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019