December 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9810) Fix testUpdatingTTLOnAccessingData test

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9810?page=com.atlassian.jira.plugin.... ] Work on ISPN-9810 started by Katia Aresti. ------------------------------------------ > Fix testUpdatingTTLOnAccessingData test > --------------------------------------- > > Key: ISPN-9810 > URL: https://issues.jboss.org/browse/ISPN-9810 > Project: Infinispan > Issue Type: Task > Components: Spring Integration > Affects Versions: 10.0.0.Alpha2, 9.4.4.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.5.Final > > > InfinispanApplicationPublishedBridgeTCK.testEventBridge > Fails in remote randomly. > This failure is related to the fact that spring session API's have changed. Now to send an event to spring context we need to send the session object instead of the ID. > In the case of this test, we safe two sessions and remove 1. > After a while, we will verify if 2 creation events and 1 deletion event has been fired. > If the creation and removal happens faster than the listener getting notified and retrieving the session object to send the notification to spring, the creation event won't be fired ( (remote get will be null in this case), so we will have 1 event instead of two. > The test must be changed to meet this case. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9809) Added version.component.console

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9809?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9809: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/6528, https://github.com/infinispan/infinispan/pull/6529 (was: https://github.com/infinispan/infinispan/pull/6528) > Added version.component.console > ------------------------------- > > Key: ISPN-9809 > URL: https://issues.jboss.org/browse/ISPN-9809 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.4.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.5.Final > > > There is a patch that injects `version.component.console` property to the pom.xml to update the console in Infinispan. However, when the console updates, the patch fails to apply. Added the property upstream to avoid future issues... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9809) Added version.component.console

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9809?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9809: ------------------------------ Status: Open (was: New) > Added version.component.console > ------------------------------- > > Key: ISPN-9809 > URL: https://issues.jboss.org/browse/ISPN-9809 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.4.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.5.Final > > > There is a patch that injects `version.component.console` property to the pom.xml to update the console in Infinispan. However, when the console updates, the patch fails to apply. Added the property upstream to avoid future issues... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9809) Added version.component.console

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9809?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9809: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6528 > Added version.component.console > ------------------------------- > > Key: ISPN-9809 > URL: https://issues.jboss.org/browse/ISPN-9809 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.4.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.5.Final > > > There is a patch that injects `version.component.console` property to the pom.xml to update the console in Infinispan. However, when the console updates, the patch fails to apply. Added the property upstream to avoid future issues... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9809) Added version.component.console

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9809?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-9809: ----------------------------------- ps. needs fixes upstream and downstream :( > Added version.component.console > ------------------------------- > > Key: ISPN-9809 > URL: https://issues.jboss.org/browse/ISPN-9809 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha2, 9.4.4.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.5.Final > > > There is a patch that injects `version.component.console` property to the pom.xml to update the console in Infinispan. However, when the console updates, the patch fails to apply. Added the property upstream to avoid future issues... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9809) Added version.component.console

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-9809: --------------------------------- Summary: Added version.component.console Key: ISPN-9809 URL: https://issues.jboss.org/browse/ISPN-9809 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.4.4.Final, 10.0.0.Alpha2 Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 10.0.0.Beta1, 9.4.5.Final There is a patch that injects `version.component.console` property to the pom.xml to update the console in Infinispan. However, when the console updates, the patch fails to apply. Added the property upstream to avoid future issues... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9801) ClusterTopologyManagerImpl hangs when restarting a node with FORK

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9801?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9801: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6527 My "reproducer" had a bug: it was connecting the joiner's {{JChannel}} before adding a {{FORK}} protocol, and implicitly before adding the required {{UnknownForkHandler}}. Once I changed it to add the {{FORK}} first, I was no longer able to reproduce the failure. I still don't know what was causing the problem reported in the forum post, so I made some small improvements to {{ClusterTopologyManagerImpl}}'s view handling so it can handle new views even if some members of an old view are not responding. > ClusterTopologyManagerImpl hangs when restarting a node with FORK > ----------------------------------------------------------------- > > Key: ISPN-9801 > URL: https://issues.jboss.org/browse/ISPN-9801 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha1, 9.4.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.5.Final > > > When a server is restarted with `kill -9` or similar, both the old node and the new one can be in the JGroups view for a while. Normally this shouldn't be a problem, but sometimes the new node doesn't receive the {{HeartBeatCommand}} and the coordinator cannot process any new view updates. > {noformat} > 14:29:19,981 INFO (jgroups-12,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [ClusterTopologyManagerImpl] Updating cluster members for all the caches. New list is [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [JGroupsTransport] Test-NodeA sending request 9 to all: org.infinispan.topology.HeartBeatCommand@1163beb6 > 14:29:19,986 TRACE (jgroups-6,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeC: SuccessfulResponse(null) > 14:29:19,987 TRACE (jgroups-9,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeD: SuccessfulResponse(null) > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [TCP_NIO2] Test-NodeE: received message batch of 1 messages from Test-NodeA > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: message Test-NodeA::39 was added to queue (not yet server) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: received Test-NodeA#38 > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: delivering Test-NodeA#38 > # not actually delivered :) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [MFC] Test-NodeA used 5 credits, 1999995 remaining > 14:29:20,149 INFO (ForkThread-1,ForkChannelRestartTest:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:21,119 DEBUG (testng-Test-1:[]) [ForkChannelRestartTest] Stopping channel Test-NodeB > 14:29:23,319 INFO (VERIFY_SUSPECT.TimerThread-32,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|5] (4) [Test-NodeA, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:23,320 TRACE (remote-thread-Test-NodeA-p2-t1:[]) [MultiTargetRequest] Target Test-NodeB of request 9 left the cluster view > {noformat} > So far, it looks like it's a JGroups bug similar to JGRP-2294, but we need to investigate further. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9735) InfinispanCacheMeterBinderProvider is always created and causes CastException if infinispan is not enabled

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9735?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9735: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-spring-boot/pull/83 > InfinispanCacheMeterBinderProvider is always created and causes CastException if infinispan is not enabled > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-9735 > URL: https://issues.jboss.org/browse/ISPN-9735 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > The InfinispanCacheMeterBinderProvider Actuator cast to the native Cache always if bean exist. > This is the Case if you depend on the starter. > But if you change the cache type in Spring to 'simple' this binder will cause an Class Cast Exception. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[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: ------------------------------- Fix Version/s: 9.4.5.Final > 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

1
0
0 / 0

[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: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6526 > 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2018