March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9631) REST API should return 503 Service Unavailable if store's becomes unavailable

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9631?page=com.atlassian.jira.plugin.... ] Diego Lovison reassigned ISPN-9631: ----------------------------------- Assignee: Diego Lovison (was: Ryan Emerson) > REST API should return 503 Service Unavailable if store's becomes unavailable > ----------------------------------------------------------------------------- > > Key: ISPN-9631 > URL: https://issues.jboss.org/browse/ISPN-9631 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Diego Lovison > Priority: Major > > The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present. > AbstractOperations::createResponseException should be modified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9631) REST API should return 503 Service Unavailable if store's becomes unavailable

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9631?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9631: -------------------------------- Status: Open (was: New) > REST API should return 503 Service Unavailable if store's becomes unavailable > ----------------------------------------------------------------------------- > > Key: ISPN-9631 > URL: https://issues.jboss.org/browse/ISPN-9631 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Diego Lovison > Priority: Major > > The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present. > AbstractOperations::createResponseException should be modified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

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 reassigned ISPN-10073: -------------------------------------- Assignee: William Burns > 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 = 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)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10069) Contribute to Operator Quickstart

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10069?page=com.atlassian.jira.plugin... ] Don Naro updated ISPN-10069: ---------------------------- Status: Open (was: New) > Contribute to Operator Quickstart > --------------------------------- > > Key: ISPN-10069 > URL: https://issues.jboss.org/browse/ISPN-10069 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > https://github.com/infinispan/infinispan-simple-tutorials/tree/master/ope... > Change Step 1 to either install manually or via operatorhub.io -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10069) Contribute to Operator Quickstart

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10069?page=com.atlassian.jira.plugin... ] Don Naro updated ISPN-10069: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-simple-tutorials/pull/69 > Contribute to Operator Quickstart > --------------------------------- > > Key: ISPN-10069 > URL: https://issues.jboss.org/browse/ISPN-10069 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > https://github.com/infinispan/infinispan-simple-tutorials/tree/master/ope... > Change Step 1 to either install manually or via operatorhub.io -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10069) Contribute to Operator Quickstart

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10069?page=com.atlassian.jira.plugin... ] Don Naro updated ISPN-10069: ---------------------------- Component/s: Operator > Contribute to Operator Quickstart > --------------------------------- > > Key: ISPN-10069 > URL: https://issues.jboss.org/browse/ISPN-10069 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core, Operator > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > https://github.com/infinispan/infinispan-simple-tutorials/tree/master/ope... > Change Step 1 to either install manually or via operatorhub.io -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10027) Operator README

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10027?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10027: ------------------------------------ Component/s: Operator > Operator README > --------------- > > Key: ISPN-10027 > URL: https://issues.jboss.org/browse/ISPN-10027 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core, Operator > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10027) Operator README

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-10027?page=com.atlassian.jira.plugin... ] Galder Zamarreño updated ISPN-10027: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Operator README > --------------- > > Key: ISPN-10027 > URL: https://issues.jboss.org/browse/ISPN-10027 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core, Operator > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 2 months

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} 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)

5 years, 2 months

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)

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019