[JBoss JIRA] (ISPN-7783) ClassCastException in case of configured read-through cache with some cache loader
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7783?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7783:
-----------------------------------
Fix Version/s: 9.1.0.Final
9.0.1.Final
9.1.0.Alpha1
> ClassCastException in case of configured read-through cache with some cache loader
> ----------------------------------------------------------------------------------
>
> Key: ISPN-7783
> URL: https://issues.jboss.org/browse/ISPN-7783
> Project: Infinispan
> Issue Type: Bug
> Components: JCache
> Affects Versions: 8.2.1.Final, 9.0.0.Final
> Reporter: Roman Chigvintsev
> Fix For: 9.1.0.Final, 9.0.1.Final, 9.1.0.Alpha1
>
>
> When cache is configured through JCache API as a read-through cache with some cache loader Infinispan puts cache values provided by that loader in place of keys. It causes `java.lang.ClassCastException` after calling of `javax.cache.Cache.removeAll` method. Iteration on cache also turns out to be broken.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (ISPN-7773) OSGiKarafFeaturesTest.testCleanInstall fails
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7773?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7773:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.1.0.Final
9.1.0.Alpha1
Resolution: Done
> OSGiKarafFeaturesTest.testCleanInstall fails
> --------------------------------------------
>
> Key: ISPN-7773
> URL: https://issues.jboss.org/browse/ISPN-7773
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
> Fix For: 9.1.0.Final, 9.1.0.Alpha1
>
>
> {noformat}
> Can't install feature infinispan-embedded/9.1.0-SNAPSHOT:
> Could not start bundle mvn:org.infinispan/infinispan-embedded/9.1.0-SNAPSHOT in feature(s) infinispan-embedded-9.1.0-SNAPSHOT: Unresolved constraint in bundle org.infinispan.embedded [136]: Unable to resolve 136.0: missing requirement [136.0] osgi.wiring.package; (&(osgi.wiring.package=javassist)(version>=3.20.0)(!(version>=4.0.0)))
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (ISPN-7800) Cluster always in Degraded Mode
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-7800?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-7800:
------------------------------
Forum Reference: https://developer.jboss.org/message/971397#971397
> Cluster always in Degraded Mode
> -------------------------------
>
> Key: ISPN-7800
> URL: https://issues.jboss.org/browse/ISPN-7800
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.2.6.Final, 9.0.0.Final
> Reporter: Pedro Ruivo
>
> Scenario:
> * 3 nodes, server mode with Partition handling enabled
> * 2 nodes are killed and bring back online
> * the nodes are unable to merge and the cluster remains in degraded mode.
> I suspect that the FORK channel/protocol is the culprit since the heartbeat command is never handled in the joiner node, but the coordinator receives a {{CacheNotFoundResponse}} quickly (i.e. without timeout). The request is received and "delivered" but never reaches Infinispan.
> When starting node 1 (logs from coordinator):
> {code}
> Received new cluster view: 5, isCoordinator = true, old status = COORDINATOR
> Received new cluster view: 5, isCoordinator = true, old status = COORDINATOR
> //hearbeat sent, ClusterTopologyManagerImpl.confirmMembersAvailable();
> Responses: value=CacheNotFoundResponse, received=true, suspected=false
> Node node01-47572 left while updating cache members
> //the view is not handled
> {code}
> When I started node 2:
> {code}
> Received new cluster view: 6, isCoordinator = true, old status = COORDINATOR
> Updating cluster members for all the caches. New list is [node03-48579, node01-47572, node02-32959]
> //hearbeat sent, ClusterTopologyManagerImpl.confirmMembersAvailable();
> Responses: Responses{
> node01-47572: value=SuccessfulResponse{responseValue=true} , received=true, suspected=false
> node02-32959: value=CacheNotFoundResponse, received=true, suspected=false}
> Node node02-32959 left while updating cache members
> //the view is not handled
> {code}
> It is always reproducible. The configuration is
> {code:xml}
> <replicated-cache name="default" mode="SYNC" batching="true">
> <partition-handling enabled="true"/>
> <locking isolation="REPEATABLE_READ"/>
> <state-transfer enabled="false"/>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (ISPN-7800) Cluster always in Degraded Mode
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-7800:
---------------------------------
Summary: Cluster always in Degraded Mode
Key: ISPN-7800
URL: https://issues.jboss.org/browse/ISPN-7800
Project: Infinispan
Issue Type: Bug
Affects Versions: 9.0.0.Final, 8.2.6.Final
Reporter: Pedro Ruivo
Scenario:
* 3 nodes, server mode with Partition handling enabled
* 2 nodes are killed and bring back online
* the nodes are unable to merge and the cluster remains in degraded mode.
I suspect that the FORK channel/protocol is the culprit since the heartbeat command is never handled in the joiner node, but the coordinator receives a {{CacheNotFoundResponse}} quickly (i.e. without timeout). The request is received and "delivered" but never reaches Infinispan.
When starting node 1 (logs from coordinator):
{code}
Received new cluster view: 5, isCoordinator = true, old status = COORDINATOR
Received new cluster view: 5, isCoordinator = true, old status = COORDINATOR
//hearbeat sent, ClusterTopologyManagerImpl.confirmMembersAvailable();
Responses: value=CacheNotFoundResponse, received=true, suspected=false
Node node01-47572 left while updating cache members
//the view is not handled
{code}
When I started node 2:
{code}
Received new cluster view: 6, isCoordinator = true, old status = COORDINATOR
Updating cluster members for all the caches. New list is [node03-48579, node01-47572, node02-32959]
//hearbeat sent, ClusterTopologyManagerImpl.confirmMembersAvailable();
Responses: Responses{
node01-47572: value=SuccessfulResponse{responseValue=true} , received=true, suspected=false
node02-32959: value=CacheNotFoundResponse, received=true, suspected=false}
Node node02-32959 left while updating cache members
//the view is not handled
{code}
It is always reproducible. The configuration is
{code:xml}
<replicated-cache name="default" mode="SYNC" batching="true">
<partition-handling enabled="true"/>
<locking isolation="REPEATABLE_READ"/>
<state-transfer enabled="false"/>
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[JBoss JIRA] (ISPN-7680) [OSGi] Enable karaf-maven-plugin
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7680?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7680:
-----------------------------------
Fix Version/s: 9.1.0.Final
9.1.0.Alpha1
> [OSGi] Enable karaf-maven-plugin
> --------------------------------
>
> Key: ISPN-7680
> URL: https://issues.jboss.org/browse/ISPN-7680
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 9.0.0.CR3
> Reporter: Paolo Antinori
> Assignee: Galder Zamarreño
> Fix For: 9.1.0.Final, 9.1.0.Alpha1
>
>
> Enabling {{org.apache.karaf.tooling:karaf-maven-plugin:verify}} allows to validate Karaf {{features.xml}}.
> Validation assures that the feature definition declares all its dependencies so to be able to installed in complete isolation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years