[JBoss JIRA] (ISPN-9807) SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failure
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9807?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9807:
-------------------------------
Status: Open (was: New)
> SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failure
> --------------------------------------------------------------------------------
>
> Key: ISPN-9807
> URL: https://issues.jboss.org/browse/ISPN-9807
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 10.0.0.Alpha2, 9.4.4.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta1, 9.4.5.Final
>
>
> {noformat}
> testExecutorTriConsumerTimeoutException[false](org.infinispan.manager.SingleClusterExecutorTest) Time elapsed: 0.033 s <<< FAILURE!
> java.lang.NullPointerException
> at org.infinispan.remoting.transport.AbstractRequest.setTimeoutFuture(AbstractRequest.java:94)
> at org.infinispan.remoting.transport.AbstractRequest.setTimeout(AbstractRequest.java:55)
> at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeCommand(JGroupsTransport.java:831)
> at org.infinispan.manager.impl.SingleClusterExecutor.submitConsumer(SingleClusterExecutor.java:136)
> at org.infinispan.manager.ClusterExecutor.submitConsumer(ClusterExecutor.java:116)
> at org.infinispan.manager.AllClusterExecutorTest$17.call(AllClusterExecutorTest.java:402)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1593)
> at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:382)
> {noformat}
> The mock {{ScheduledExecutorService}} returns a {{null}} future, causing a {{NullPointerException}} when the request is already done and the timeout future needs to be cancelled. Can be reproduced reliably by adding a delay before {{isDone()}} in {{AbstractRequest.setTimeoutFuture()}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4075:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6525
> State transfer should preserve the creation timestamp of entries
> ----------------------------------------------------------------
>
> Key: ISPN-4075
> URL: https://issues.jboss.org/browse/ISPN-4075
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta1, 10.0.0.Final
>
>
> State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended.
> The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4075:
-------------------------------
Fix Version/s: 10.0.0.Beta1
> State transfer should preserve the creation timestamp of entries
> ----------------------------------------------------------------
>
> Key: ISPN-4075
> URL: https://issues.jboss.org/browse/ISPN-4075
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta1, 10.0.0.Final
>
>
> State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended.
> The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9808) Cluster executor commands don't end in Command
by Dan Berindei (Jira)
Dan Berindei created ISPN-9808:
----------------------------------
Summary: Cluster executor commands don't end in Command
Key: ISPN-9808
URL: https://issues.jboss.org/browse/ISPN-9808
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.4.4.Final, 10.0.0.Alpha2
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 10.0.0.Beta1
Because they don't follow the naming convention of ending in {{Command}}, the {{bin/list_command_ids.py}} doesn't show cluster executor commands.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9807) SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failure
by Dan Berindei (Jira)
Dan Berindei created ISPN-9807:
----------------------------------
Summary: SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failure
Key: ISPN-9807
URL: https://issues.jboss.org/browse/ISPN-9807
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core
Affects Versions: 9.4.4.Final, 10.0.0.Alpha2
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 10.0.0.Beta1
{noformat}
testExecutorTriConsumerTimeoutException[false](org.infinispan.manager.SingleClusterExecutorTest) Time elapsed: 0.033 s <<< FAILURE!
java.lang.NullPointerException
at org.infinispan.remoting.transport.AbstractRequest.setTimeoutFuture(AbstractRequest.java:94)
at org.infinispan.remoting.transport.AbstractRequest.setTimeout(AbstractRequest.java:55)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeCommand(JGroupsTransport.java:831)
at org.infinispan.manager.impl.SingleClusterExecutor.submitConsumer(SingleClusterExecutor.java:136)
at org.infinispan.manager.ClusterExecutor.submitConsumer(ClusterExecutor.java:116)
at org.infinispan.manager.AllClusterExecutorTest$17.call(AllClusterExecutorTest.java:402)
at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1593)
at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:382)
{noformat}
The mock {{ScheduledExecutorService}} returns a {{null}} future, causing a {{NullPointerException}} when the request is already done and the timeout future needs to be cancelled. Can be reproduced reliably by adding a delay before {{isDone()}} in {{AbstractRequest.setTimeoutFuture()}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months