[JBoss JIRA] (ISPN-3868) Deadlock in RemoteCache getAsync
by Alan Feng (JIRA)
[ https://issues.jboss.org/browse/ISPN-3868?page=com.atlassian.jira.plugin.... ]
Alan Feng commented on ISPN-3868:
---------------------------------
May I ask why the fix for this critical issue is not back ported to the 6.x releases, which is used in most of places?
> Deadlock in RemoteCache getAsync
> --------------------------------
>
> Key: ISPN-3868
> URL: https://issues.jboss.org/browse/ISPN-3868
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 6.0.0.Final
> Environment: RemoteCahe component of 6.0.0.Final
> Reporter: Alexander Furer
> Assignee: Mircea Markus
> Labels: 630, remote
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
>
> Here is the implementation of remoteCahe.getAsync() :
> {code}
> public NotifyingFuture<V> getAsync(final K key) {
> assertRemoteCacheManagerIsStarted();
> final NotifyingFutureImpl<V> result = new NotifyingFutureImpl<V>();
> Future<V> future = executorService.submit(new Callable<V>() {
> @Override
> public V call() throws Exception {
> V toReturn = get(key);
> result.notifyFutureCompletion();
> return toReturn;
> }
> });
> result.setExecuting(future);
> return result;
> }
> {code}
> 2 problems here :
> 1. Callable's call method might be called BEFORE calling client had a chance to add listener (i.e. getAsync is not returned yet), in this case its' listener futureDone method will never be called.
> 2. Even case #1 has not happened and notifyFutureCompletion is called on listener, but the future is not resolved yet : "call" has not returned, that's why the future that is passed to listener is not resolved, and calling future.get from listener blocks forever.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4744) RemoteCacheOsgiIT fails to run
by Ion Savin (JIRA)
[ https://issues.jboss.org/browse/ISPN-4744?page=com.atlassian.jira.plugin.... ]
Ion Savin updated ISPN-4744:
----------------------------
Description:
Three problems:
* the 3 nodes started using antrun fail to start if JBOSS_HOME is set to a location different from the ones holding the configs (target/server/node{1,2,3})
* the test probe doesn't export the Person class used in the test and commons fails to find this class
* paxurl fails to find the osgi features if custom maven local repository paths are used
was:
Two problems:
* the 3 nodes started using antrun fail to start if JBOSS_HOME is set to a location different from the ones holding the configs (target/server/node{1,2,3})
* the test probe doesn't export the Person class used in the test and commons fails to find this class
> RemoteCacheOsgiIT fails to run
> ------------------------------
>
> Key: ISPN-4744
> URL: https://issues.jboss.org/browse/ISPN-4744
> Project: Infinispan
> Issue Type: Task
> Affects Versions: 7.0.0.Beta2
> Reporter: Adrian Nistor
> Assignee: Ion Savin
> Fix For: 7.0.0.Final
>
>
> Three problems:
> * the 3 nodes started using antrun fail to start if JBOSS_HOME is set to a location different from the ones holding the configs (target/server/node{1,2,3})
> * the test probe doesn't export the Person class used in the test and commons fails to find this class
> * paxurl fails to find the osgi features if custom maven local repository paths are used
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4744) RemoteCacheOsgiIT fails to run
by Ion Savin (JIRA)
Ion Savin created ISPN-4744:
-------------------------------
Summary: RemoteCacheOsgiIT fails to run
Key: ISPN-4744
URL: https://issues.jboss.org/browse/ISPN-4744
Project: Infinispan
Issue Type: Task
Affects Versions: 7.0.0.Beta2
Reporter: Adrian Nistor
Assignee: Ion Savin
Fix For: 7.0.0.Final
Two problems:
* the 3 nodes started using antrun fail to start if JBOSS_HOME is set to a location different from the ones holding the configs (target/server/node{1,2,3})
* the test probe doesn't export the Person class used in the test and commons fails to find this class
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-4743) Rebalance can hang after the coordinator and another node leave
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4743:
----------------------------------
Summary: Rebalance can hang after the coordinator and another node leave
Key: ISPN-4743
URL: https://issues.jboss.org/browse/ISPN-4743
Project: Infinispan
Issue Type: Bug
Components: Core, State Transfer
Affects Versions: 7.0.0.Beta2
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 7.0.0.CR1
This caused a failure in {{ClusterTopologyManagerTest.testAbruptLeaveAfterGetStatus}}.
When the coordinator changes, the new coordinator first sends a {{CacheTopologyControlCommand(type=CH_UPDATE)}} to reset any ongoing rebalance, then a {{CacheTopologyControlCommand(type=REBALANCE_START)}} to start a new rebalance with the remaining members. If another node leaves afterwards, the coordinator sends yet another {{CacheTopologyControlCommand(type=CH_UPDATE)}} to remove the leaver from the CHs.
If one node (in this case the coordinator itself) processes the last {{CH_UPDATE}} before the other two commands, it will fail to confirm the rebalance, and the cache will stay in "rebalancing" state until another node joins or leaves.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-3402) Add JDBC Cache Store config to RHQ plugin
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-3402?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-3402:
--------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2888
> Add JDBC Cache Store config to RHQ plugin
> -----------------------------------------
>
> Key: ISPN-3402
> URL: https://issues.jboss.org/browse/ISPN-3402
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores, Server
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.CR1
>
>
> ISPN-3350 was added to enhance some of the RHQ endpoints to allow for better runtime configuration support. However ISPN-3290 is also concurrently changing cache stores. Some changes for ISPN-3290 were mentioned to be possibly changing how the JDBC cache stores are configured and as such this has been excluded from ISPN-3350 to not implement it twice.
> This is just to add in the support JDBC cache stores as they are missing.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-3402) Add JDBC Cache Store config to RHQ plugin
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3402?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3402:
-----------------------------------------------
William Burns <wburns(a)redhat.com> changed the Status of [bug 1144491|https://bugzilla.redhat.com/show_bug.cgi?id=1144491] from NEW to POST
> Add JDBC Cache Store config to RHQ plugin
> -----------------------------------------
>
> Key: ISPN-3402
> URL: https://issues.jboss.org/browse/ISPN-3402
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores, Server
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.CR1
>
>
> ISPN-3350 was added to enhance some of the RHQ endpoints to allow for better runtime configuration support. However ISPN-3290 is also concurrently changing cache stores. Some changes for ISPN-3290 were mentioned to be possibly changing how the JDBC cache stores are configured and as such this has been excluded from ISPN-3350 to not implement it twice.
> This is just to add in the support JDBC cache stores as they are missing.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-3402) Add JDBC Cache Store config to RHQ plugin
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3402?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-3402:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1144491
> Add JDBC Cache Store config to RHQ plugin
> -----------------------------------------
>
> Key: ISPN-3402
> URL: https://issues.jboss.org/browse/ISPN-3402
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores, Server
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.CR1
>
>
> ISPN-3350 was added to enhance some of the RHQ endpoints to allow for better runtime configuration support. However ISPN-3290 is also concurrently changing cache stores. Some changes for ISPN-3290 were mentioned to be possibly changing how the JDBC cache stores are configured and as such this has been excluded from ISPN-3350 to not implement it twice.
> This is just to add in the support JDBC cache stores as they are missing.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (ISPN-3402) Add JDBC Cache Store config to RHQ plugin
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-3402?page=com.atlassian.jira.plugin.... ]
William Burns commented on ISPN-3402:
-------------------------------------
Map within maps isn't currently supported in RHQ on the agent code side. I submitted https://github.com/rhq-project/rhq/pull/128 to fix this. However the fix I have for now just overrides the method from RHQ to get the proper behavior until we get a version of RHQ with it fixed.
> Add JDBC Cache Store config to RHQ plugin
> -----------------------------------------
>
> Key: ISPN-3402
> URL: https://issues.jboss.org/browse/ISPN-3402
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores, Server
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 7.0.0.CR1
>
>
> ISPN-3350 was added to enhance some of the RHQ endpoints to allow for better runtime configuration support. However ISPN-3290 is also concurrently changing cache stores. Some changes for ISPN-3290 were mentioned to be possibly changing how the JDBC cache stores are configured and as such this has been excluded from ISPN-3350 to not implement it twice.
> This is just to add in the support JDBC cache stores as they are missing.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months