[JBoss JIRA] (ISPN-4200) ExampleConfigsTest.testRestRollingUpgrades fails
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4200?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4200:
-----------------------------------------------
Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 1086180|https://bugzilla.redhat.com/show_bug.cgi?id=1086180] from NEW to POST
> ExampleConfigsTest.testRestRollingUpgrades fails
> ------------------------------------------------
>
> Key: ISPN-4200
> URL: https://issues.jboss.org/browse/ISPN-4200
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 7.0.0.Beta1
> Reporter: Jakub Markos
> Assignee: Martin Gencur
> Fix For: 7.0.0.Beta2
>
>
> Fails in the latest snapshot on line 240 with
> {code}
> Can't access etries stored in source node (target's RestCacheStore). expected:<value1> but was:<[B@19676adb>
> {code}
> you can run the test from /server/integration/testsuite with this command:
> mvn clean test -Psuite.examples -Dtest=ExampleConfigsTest#testRestRollingUpgrades
> The configs used are /server/integration/testsuite/target/server/node1/standalone/configuration/examples/{standalone-rest-rolling-upgrade.xml, standalone-compatibility-mode.xml}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (ISPN-5061) Cross site state transfer - NPE on consumer site when backup cache is local
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5061?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5061:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.1.0.Final
Resolution: Done
> Cross site state transfer - NPE on consumer site when backup cache is local
> ---------------------------------------------------------------------------
>
> Key: ISPN-5061
> URL: https://issues.jboss.org/browse/ISPN-5061
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.1.0.Alpha1
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
> Fix For: 7.1.0.Beta1, 7.1.0.Final
>
>
> NPE detected on consumer site after invoking push operation on producer site. Occurs when corresponding cache does not exist on consumer site (either with the same name as the main cache or specified via <backup-for> option).
> Configuration:
> 2 sites, BRN (main), LON (backup)
> Producer site CLI:
> Unable to pushState to 'LON'. org.infinispan.commons.CacheException: Problems invoking command.
> Consumer site log:
> 11:18:45,245 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (remote-thread--p3-t1) ISPN000071: Caught exception when handling command XSiteStateTransferControlCommand{control=START_RECEIVE, siteName='LON', statusOk=false, cacheName='lonCache'}: java.lang.NullPointerException
> at org.infinispan.xsite.BackupReceiverImpl.invokeRemotelyInLocalSite(BackupReceiverImpl.java:213) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.BackupReceiverImpl.handleStateTransferControl(BackupReceiverImpl.java:90) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.statetransfer.XSiteStateTransferControlCommand.performInLocalSite(XSiteStateTransferControlCommand.java:41) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$3.run(CommandAwareRpcDispatcher.java:252) [infinispan-core.jar:7.1.0.Alpha1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]
> 11:18:45,420 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (remote-thread--p3-t1) ISPN000071: Caught exception when handling command XSiteStateTransferControlCommand{control=FINISH_RECEIVE, siteName='LON', statusOk=false, cacheName='lonCache'}: java.lang.NullPointerException
> at org.infinispan.xsite.BackupReceiverImpl.invokeRemotelyInLocalSite(BackupReceiverImpl.java:213) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.BackupReceiverImpl.handleStateTransferControl(BackupReceiverImpl.java:90) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.xsite.statetransfer.XSiteStateTransferControlCommand.performInLocalSite(XSiteStateTransferControlCommand.java:41) [infinispan-core.jar:7.1.0.Alpha1]
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$3.run(CommandAwareRpcDispatcher.java:252) [infinispan-core.jar:7.1.0.Alpha1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (ISPN-5060) PartitionHandling: remove unavailable mode
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5060?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5060:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.1.0.Beta1
Resolution: Done
> PartitionHandling: remove unavailable mode
> ------------------------------------------
>
> Key: ISPN-5060
> URL: https://issues.jboss.org/browse/ISPN-5060
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Beta1, 7.1.0.Final
>
>
> The Unavailable mode name is misleading, because some keys are available, just like in Degraded mode.
> The only difference between Degraded and Unavailable is that with Degraded the cluster might recover without manual intervention. The administrator still has to know a lot more details in order to decide whether manual intervention is needed or not. So it would be less confusing if gracefully shutting down {{numOwners}} nodes in quick succession would leave the cache in Degraded mode instead of Unavailable.
> Instead of removing the Unavailable mode completely, we could also change it to deny access to all the keys and allow the administrator to use it. E.g. if we had an operation to dump the cache into a shared store and another to load the cache from a shared store, the administrator could force the cache into Unavailable mode while dumping/loading the cache.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months