]
William Burns commented on ISPN-10073:
--------------------------------------
[~jbtrystram]I am not sure how we want to fix this yet, but you should be able to
workaround this easily by making sure you don't perform blocking operations inside the
callback from the CompletableFuture or by transferring execution over to a different
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.