[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by Vittorio Rigamonti (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
Vittorio Rigamonti updated ISPN-6071:
-------------------------------------
Fix Version/s: 9.0.0.Alpha2
(was: 9.0.0.Alpha1)
> NullPointerException when executing RemoveExpiredCommand
> --------------------------------------------------------
>
> Key: ISPN-6071
> URL: https://issues.jboss.org/browse/ISPN-6071
> Project: Infinispan
> Issue Type: Bug
> Components: Expiration
> Affects Versions: 8.0.2.Final
> Reporter: Jason Hoetger
> Assignee: William Burns
> Fix For: 9.0.0.Alpha2, 8.1.4.Final, 8.2.2.Final
>
>
> I'm running Infinispan 8.0.2 in a clustered environment with a replicated cache with a single file cache store. I'm seeing some NullPointerExceptions when Infinispan executes the RemoveExpiredCommand. Here's a snippet from the stack trace:
> {noformat}
> ISPN000136: Error executing command RemoveExpiredCommand, writing keys [...large key here...]
> ...
> Caused by: java.lang.NullPointerException: null
> at org.infinispan.commands.write.RemoveExpiredCommand.setParameters(RemoveExpiredCommand.java:142)
> {noformat}
> Here's RemoveExpiredCommand#setParameters(...):
> {code} @Override
> public void setParameters(int commandId, Object[] args) {
> if (commandId != COMMAND_ID) throw new IllegalStateException("Invalid method id");
> int i = 0;
> commandInvocationId = (CommandInvocationId) args[i++];
> key = args[i++];
> value = args[i++];
> lifespan = (long) args[i++];
> }{code}
> Line 142 is the cast of assignment of {{args\[3\]}} to primitive type long, which is causing the NPE. lifespan is actually a Long, not a long, and the {{perform()}} method seems to anticipate null lifespans at line 72:
> {code} // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}{code}
> Could this be fixed by simply changing the cast at line 142 from (long) to (Long)?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (ISPN-6039) NonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringPutOverwrite random failures
by Vittorio Rigamonti (JIRA)
[ https://issues.jboss.org/browse/ISPN-6039?page=com.atlassian.jira.plugin.... ]
Vittorio Rigamonti updated ISPN-6039:
-------------------------------------
Fix Version/s: 9.0.0.Alpha2
(was: 9.0.0.Alpha1)
> NonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringPutOverwrite random failures
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-6039
> URL: https://issues.jboss.org/browse/ISPN-6039
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 8.1.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 9.0.0.Alpha2
>
>
> The problem is that the state transfer write can happen after we started the regular put, and is blocked by the {{BlockingInterceptor}}. The test then unblocks the state transfer put, but never unblocks the regular put, which eventually times out.
> {noformat}
> java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:205)
> at org.infinispan.distribution.rehash.NonTxBackupOwnerBecomingPrimaryOwnerTest.doTest(NonTxBackupOwnerBecomingPrimaryOwnerTest.java:193)
> at org.infinispan.distribution.rehash.NonTxBackupOwnerBecomingPrimaryOwnerTest.testPrimaryOwnerChangingDuringPutOverwrite(NonTxBackupOwnerBecomingPrimaryOwnerTest.java:75)
> {noformat}
> The test should be more explicit about the state transfer put - ideally it should have 2 cases, one with the state transfer put happening before the regular put, and one after.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (ISPN-6038) ClientAsymmetricClusterTest.testAsymmetricCluster random failures
by Vittorio Rigamonti (JIRA)
[ https://issues.jboss.org/browse/ISPN-6038?page=com.atlassian.jira.plugin.... ]
Vittorio Rigamonti updated ISPN-6038:
-------------------------------------
Fix Version/s: 9.0.0.Alpha2
(was: 9.0.0.Alpha1)
> ClientAsymmetricClusterTest.testAsymmetricCluster random failures
> -----------------------------------------------------------------
>
> Key: ISPN-6038
> URL: https://issues.jboss.org/browse/ISPN-6038
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols, Test Suite - Server
> Reporter: Dan Berindei
> Assignee: Galder Zamarreño
> Priority: Minor
> Labels: testsuite_stability
> Fix For: 9.0.0.Alpha2
>
>
> {{ClientAsymmetricClusterTest.testAsymmetricCluster}} is failing since the ISPN-5981 fix, which enabled {{pingOnStartup}} by default, and now returns {{null}} if the first server to be pinged doesn't have the cache defined.
> {noformat}
> 10:23:07,862 WARN (testng-ClientAsymmetricClusterTest:) [Codec21] ISPN004005: Error received from the server: org.infinispan.server.hotrod.CacheNotFoundException: Cache with name 'asymmetricCache' not found amongst the configured caches
> 10:23:07,862 ERROR (testng-ClientAsymmetricClusterTest:) [UnitTestTestNGListener] Test testAsymmetricCluster(org.infinispan.client.hotrod.ClientAsymmetricClusterTest) failed.
> java.lang.NullPointerException
> at org.infinispan.client.hotrod.ClientAsymmetricClusterTest.testAsymmetricCluster(ClientAsymmetricClusterTest.java:38) ~[test-classes/:?]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months