[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6071:
--------------------------------
Fix Version/s: 9.0.0.Alpha1
8.1.4.Final
8.2.2.Final
> 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.Alpha1, 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:
> {{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)}}
> Here's RemoveExpiredCommand#setParameters(...):
> {{ @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++];
> }}}
> 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:
> {{ // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}}
> 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)
10 years
[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-6071:
--------------------------------
Status: Open (was: New)
> 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
>
> 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:
> {{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)}}
> Here's RemoveExpiredCommand#setParameters(...):
> {{ @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++];
> }}}
> 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:
> {{ // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}}
> 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)
10 years
[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
Work on ISPN-6071 started by William Burns.
-------------------------------------------
> 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
>
> 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:
> {{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)}}
> Here's RemoveExpiredCommand#setParameters(...):
> {{ @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++];
> }}}
> 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:
> {{ // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}}
> 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)
10 years
[JBoss JIRA] (ISPN-6071) NullPointerException when executing RemoveExpiredCommand
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6071?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-6071:
-------------------------------------
Assignee: William Burns
> 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
>
> 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:
> {{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)}}
> Here's RemoveExpiredCommand#setParameters(...):
> {{ @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++];
> }}}
> 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:
> {{ // If the provided lifespan is null, that means it is a store removal command, so we can't compare lifespan
> if (lifespan == null) {}}
> 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)
10 years
[JBoss JIRA] (ISPN-6235) ClusterTopologyManagerImpl join during cluster status recovery
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-6235?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6235:
----------------------------------
Affects Version/s: 8.1.3.Final
> ClusterTopologyManagerImpl join during cluster status recovery
> --------------------------------------------------------------
>
> Key: ISPN-6235
> URL: https://issues.jboss.org/browse/ISPN-6235
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 8.1.3.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Labels: testsuite_stability
> Fix For: 8.2.0.CR1
>
>
> If the joiner has the correct view id, but the current status is
> RECOVERING_CLUSTER, we should wait for the cluster status recovery to
> finish before adding the new member.
> We are currently not doing that, so the new member could be erased by the status recovery process that's in progress. This can happen if the coordinator joiner already had been a member of the JGroups cluster for some time, and there's no view change when they actually start their caches (exactly the scenario in {{ConcurrentStartTest}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-6422) ServerEventLoggerTest.testClusteredServerEventLogging fails randomly
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-6422?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-6422:
------------------------------------
Another failure, with a different exception:
{noformat}
java.lang.AssertionError: Result count discrepancy on node 0 expected:<6> but was:<4>
at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
at org.infinispan.server.eventlogger.ServerEventLoggerTest$2.call(ServerEventLoggerTest.java:87)
at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1341)
at org.infinispan.server.eventlogger.ServerEventLoggerTest.testClusteredServerEventLogging(ServerEventLoggerTest.java:66)
{noformat}
http://ci.infinispan.org/viewLog.html?buildId=38268&buildTypeId=bt9&guest=1
> ServerEventLoggerTest.testClusteredServerEventLogging fails randomly
> --------------------------------------------------------------------
>
> Key: ISPN-6422
> URL: https://issues.jboss.org/browse/ISPN-6422
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Adrian Nistor
> Assignee: Tristan Tarrant
> Fix For: 9.0.0.Alpha1
>
>
> http://ci.infinispan.org/viewLog.html?buildId=37676&tab=buildResultsDiv&b...
> {code}
> java.lang.NullPointerException: null
> at java.util.ComparableTimSort.binarySort(ComparableTimSort.java:258)
> at java.util.ComparableTimSort.sort(ComparableTimSort.java:185)
> at java.util.Arrays.sort(Arrays.java:1312)
> at java.util.Arrays.sort(Arrays.java:1506)
> at java.util.ArrayList.sort(ArrayList.java:1454)
> at java.util.Collections.sort(Collections.java:141)
> at org.infinispan.server.eventlogger.ServerEventLogger.getEvents(ServerEventLogger.java:131)
> at org.infinispan.server.eventlogger.ServerEventLoggerTest$2.call(ServerEventLoggerTest.java:86)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1348)
> at org.infinispan.server.eventlogger.ServerEventLoggerTest.testClusteredServerEventLogging(ServerEventLoggerTest.java:66)
> ------- Stdout: -------
> Configuring TestNG with: TestNG652Configurator
> Transport protocol stack used = tcp
> ------- Stderr: -------
> Mar 20, 2016 2:14:51 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport start
> INFO: ISPN000078: Starting JGroups channel ISPN
> Mar 20, 2016 2:14:51 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|0] (1) [ServerEventLoggerTest-NodeA-31008]
> Mar 20, 2016 2:14:51 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport startJGroupsChannelIfNeeded
> INFO: ISPN000079: Channel ISPN local address is ServerEventLoggerTest-NodeA-31008, physical addresses are [127.0.0.1:7900]
> Mar 20, 2016 2:14:51 AM org.infinispan.factories.GlobalComponentRegistry start
> INFO: ISPN000128: Infinispan version: Infinispan 'Chakra' 9.0.0-SNAPSHOT
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport start
> INFO: ISPN000078: Starting JGroups channel ISPN
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|1] (2) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491]
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|1] (2) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491]
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport startJGroupsChannelIfNeeded
> INFO: ISPN000079: Channel ISPN local address is ServerEventLoggerTest-NodeB-14491, physical addresses are [127.0.0.1:7901]
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport start
> INFO: ISPN000078: Starting JGroups channel ISPN
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|2] (3) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491, ServerEventLoggerTest-NodeC-47842]
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|2] (3) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491, ServerEventLoggerTest-NodeC-47842]
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|2] (3) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491, ServerEventLoggerTest-NodeC-47842]
> Mar 20, 2016 2:14:52 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport startJGroupsChannelIfNeeded
> INFO: ISPN000079: Channel ISPN local address is ServerEventLoggerTest-NodeC-47842, physical addresses are [127.0.0.1:7902]
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> INFO: message #1
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> WARN: message #2
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> INFO: message #3
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> WARN: message #4
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> INFO: message #5
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> WARN: message #6
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> INFO: message #7
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> WARN: message #8
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> INFO: message #9
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> WARN: message #10
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> INFO: message #11
> Mar 20, 2016 2:14:52 AM org.infinispan.server.eventlogger.ServerEventLogger textLog
> WARN: message #12
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport stop
> INFO: ISPN000080: Disconnecting JGroups channel ISPN
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|3] (2) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491]
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|3] (2) [ServerEventLoggerTest-NodeA-31008, ServerEventLoggerTest-NodeB-14491]
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport stop
> INFO: ISPN000082: Stopping the RpcDispatcher for channel ISPN
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport stop
> INFO: ISPN000080: Disconnecting JGroups channel ISPN
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport viewAccepted
> INFO: ISPN000094: Received new cluster view for channel ISPN: [ServerEventLoggerTest-NodeA-31008|4] (1) [ServerEventLoggerTest-NodeA-31008]
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport stop
> INFO: ISPN000082: Stopping the RpcDispatcher for channel ISPN
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport stop
> INFO: ISPN000080: Disconnecting JGroups channel ISPN
> Mar 20, 2016 2:14:53 AM org.infinispan.remoting.transport.jgroups.JGroupsTransport stop
> INFO: ISPN000082: Stopping the RpcDispatcher for channel ISPN
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years