[JBoss JIRA] (ISPN-7823) RemoteCacheManager can block waiting to connect/ping
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-7823?page=com.atlassian.jira.plugin.... ]
Katia Aresti updated ISPN-7823:
-------------------------------
Status: Open (was: New)
> RemoteCacheManager can block waiting to connect/ping
> ----------------------------------------------------
>
> Key: ISPN-7823
> URL: https://issues.jboss.org/browse/ISPN-7823
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Affects Versions: 8.2.6.Final, 9.0.0.Final
> Reporter: Galder Zamarreño
> Assignee: Katia Aresti
>
> When running Java Hot Rod client on top sensitive environments to blocking, e.g. Vert.x, you realise that the RemoteCacheManager constructor blocks.
> This is due to the fact that RCM constructor waits to establish connections with the initial servers and sends pings on startup.
> You can avoid RCM doing this by passing start=false as parameter and then calling start() manually, but start() is a blocking method.
> So, we should have an alternative start() method that returns a CompletableFuture, hence avoiding any blocking.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7823) RemoteCacheManager can block waiting to connect/ping
by Katia Aresti (JIRA)
[ https://issues.jboss.org/browse/ISPN-7823?page=com.atlassian.jira.plugin.... ]
Katia Aresti reassigned ISPN-7823:
----------------------------------
Assignee: Katia Aresti
> RemoteCacheManager can block waiting to connect/ping
> ----------------------------------------------------
>
> Key: ISPN-7823
> URL: https://issues.jboss.org/browse/ISPN-7823
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Affects Versions: 8.2.6.Final, 9.0.0.Final
> Reporter: Galder Zamarreño
> Assignee: Katia Aresti
>
> When running Java Hot Rod client on top sensitive environments to blocking, e.g. Vert.x, you realise that the RemoteCacheManager constructor blocks.
> This is due to the fact that RCM constructor waits to establish connections with the initial servers and sends pings on startup.
> You can avoid RCM doing this by passing start=false as parameter and then calling start() manually, but start() is a blocking method.
> So, we should have an alternative start() method that returns a CompletableFuture, hence avoiding any blocking.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7827) Additional Documentation for Cluster Executor
by William Burns (JIRA)
William Burns created ISPN-7827:
-----------------------------------
Summary: Additional Documentation for Cluster Executor
Key: ISPN-7827
URL: https://issues.jboss.org/browse/ISPN-7827
Project: Infinispan
Issue Type: Task
Components: Documentation-Core
Reporter: William Burns
Assignee: William Burns
Fix For: 9.1.0.Alpha1
Cluster Executor has some additional API changes. We need to document these in the user guide.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months