April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6445) PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6445?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-6445: --------------------------------------- Assignee: Dan Berindei (was: Gustavo Fernandes) > PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures > --------------------------------------------------------------------------- > > Key: ISPN-6445 > URL: https://issues.jboss.org/browse/ISPN-6445 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > The test assumes that the {{AdvancedAsyncCacheLoader.size()}} is accurate, but the implementation actually ignores the in-memory changes and just delegates to the real loader's {{size()}}. > Also, the method doesn't really belong in this test, because it doesn't use preloading. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6445) PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6445?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6445: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4191, https://github.com/infinispan/infinispan/pull/4206 (was: https://github.com/infinispan/infinispan/pull/4191) > PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures > --------------------------------------------------------------------------- > > Key: ISPN-6445 > URL: https://issues.jboss.org/browse/ISPN-6445 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > The test assumes that the {{AdvancedAsyncCacheLoader.size()}} is accurate, but the implementation actually ignores the in-memory changes and just delegates to the real loader's {{size()}}. > Also, the method doesn't really belong in this test, because it doesn't use preloading. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6462) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: Replication timeout for X

by Michal Karm Babacek (JIRA)

Michal Karm Babacek created ISPN-6462: ----------------------------------------- Summary: ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: Replication timeout for X Key: ISPN-6462 URL: https://issues.jboss.org/browse/ISPN-6462 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.1.2.Final Reporter: Michal Karm Babacek Assignee: Radoslav Husar Booting WF with starting caches yields after 1 minute: The problematic call originates in Infinispan's org.infinispan.topology.ClusterTopologyManagerImpl#confirmMembersAvailable heartbeat command. {noformat} 00:20:51,646 TRACE [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (timeout-thread--p10-t1) Response: sender=node2, received=false, suspected=false 00:20:51,647 WARN [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p13-t2) ISPN000197: Error updating cluster member list: org.infinispan.util.concurrent.TimeoutException: Replication timeout for node2 at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:765) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$0(JGroupsTransport.java:599) at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) at org.infinispan.remoting.transport.jgroups.SingleResponseFuture.call(SingleResponseFuture.java:46) at org.infinispan.remoting.transport.jgroups.SingleResponseFuture.call(SingleResponseFuture.java:17) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1068) Add usage support similar to the one included in Spring Data

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1068?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-1068: -------------------------------------- Priority: Minor (was: Major) > Add usage support similar to the one included in Spring Data > ------------------------------------------------------------ > > Key: ISPN-1068 > URL: https://issues.jboss.org/browse/ISPN-1068 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Marius Bogoevici > Assignee: Sebastian Łaskawiec > Priority: Minor > > ... i.e. InfinispanTemplate/InfinispanCallback -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6304) NPE during ClearCommand

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6304?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6304: ----------------------------------------- The NPE does not happen anymore in the hadoop tests after merging of ISPN-6460 > NPE during ClearCommand > ----------------------- > > Key: ISPN-6304 > URL: https://issues.jboss.org/browse/ISPN-6304 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.CR1, 8.2.0.Final, 8.1.2.Final > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > Fix For: 8.1.3.Final, 8.2.1.Final, 9.0.0.Alpha1 > > > The logs can be seen on https://travis-ci.org/infinispan/infinispan-hadoop/builds/113090728 > The NPE happens intermittently. > {code} > 0:52:28,139 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (HotRodServerWorker-7-1) ISPN000136: Error executing command ClearCommand, writing keys []: org.infinispan.remoting.RemoteException: ISPN000217: Received exception from node1, see cause for remote stack trace > at org.infinispan.remoting.transport.AbstractTransport.checkResponse(AbstractTransport.java:44) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:796) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$83(JGroupsTransport.java:633) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport$$Lambda$46/308539050.apply(Unknown Source) > at java.util.concurrent.CompletableFuture$ThenApply.run(CompletableFuture.java:717) > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:193) > at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2345) > at org.infinispan.remoting.transport.jgroups.SingleResponseFuture.futureDone(SingleResponseFuture.java:30) > at org.jgroups.blocks.Request.checkCompletion(Request.java:162) > at org.jgroups.blocks.UnicastRequest.receiveResponse(UnicastRequest.java:81) > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:373) > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:237) > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:695) > at org.jgroups.JChannel.up(JChannel.java:738) > at org.jgroups.fork.ForkProtocolStack.up(ForkProtocolStack.java:120) > at org.jgroups.stack.Protocol.up(Protocol.java:379) > at org.jgroups.protocols.FORK.up(FORK.java:114) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:392) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:381) > at org.jgroups.protocols.pbcast.GMS.up(GMS.java:1043) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:652) > at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:200) > at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:310) > at org.jgroups.protocols.MERGE3.up(MERGE3.java:285) > at org.jgroups.protocols.Discovery.up(Discovery.java:296) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1590) > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1802) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.infinispan.commons.CacheException: java.lang.NullPointerException > at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler.handleFromCluster(GlobalInboundInvocationHandler.java:89) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommandFromLocalCluster(CommandAwareRpcDispatcher.java:196) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:166) > at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:402) > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:352) > ... 25 more > Caused by: java.lang.NullPointerException > at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler.handleCacheRpcCommand(GlobalInboundInvocationHandler.java:126) > at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler.handleFromCluster(GlobalInboundInvocationHandler.java:75) > ... 29 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6338) Disabling cache status is lost in the UI

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6338?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6338: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.1.Final Resolution: Done > Disabling cache status is lost in the UI > ----------------------------------------- > > Key: ISPN-6338 > URL: https://issues.jboss.org/browse/ISPN-6338 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > Fix For: 8.2.1.Final > > > If you disable a cache, the disabled label appears correctly. However, if you navigate through the application, for example going back to the cache container screen, the status is lost. Entering again the cache details page shows it as enabled again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6338) Disabling cache status is lost in the UI

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6338?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6338: -------------------------------------- Status: Open (was: New) > Disabling cache status is lost in the UI > ----------------------------------------- > > Key: ISPN-6338 > URL: https://issues.jboss.org/browse/ISPN-6338 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > > If you disable a cache, the disabled label appears correctly. However, if you navigate through the application, for example going back to the cache container screen, the status is lost. Entering again the cache details page shows it as enabled again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6338) Disabling cache status is lost in the UI

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6338?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-6338: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/76 > Disabling cache status is lost in the UI > ----------------------------------------- > > Key: ISPN-6338 > URL: https://issues.jboss.org/browse/ISPN-6338 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > > If you disable a cache, the disabled label appears correctly. However, if you navigate through the application, for example going back to the cache container screen, the status is lost. Entering again the cache details page shows it as enabled again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6445) PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6445?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-6445 at 4/1/16 10:41 AM: ------------------------------------------------------------- I changed {{ParallelIterationTest}} to use an explicit executor, but forgot to remove the queue. That allowed the loader to submit all the entries to the executor before the test's task called {{TaskContext.stop()}}. was (Author: dan.berindei): I changed the test to use an explicit executor, but forgot to remove the queue. That allowed the loader to submit all the entries to the executor before the test's task called {{TaskContext.stop()}}. > PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures > --------------------------------------------------------------------------- > > Key: ISPN-6445 > URL: https://issues.jboss.org/browse/ISPN-6445 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > The test assumes that the {{AdvancedAsyncCacheLoader.size()}} is accurate, but the implementation actually ignores the in-memory changes and just delegates to the real loader's {{size()}}. > Also, the method doesn't really belong in this test, because it doesn't use preloading. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6445) PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6445?page=com.atlassian.jira.plugin.... ] Dan Berindei reopened ISPN-6445: -------------------------------- I changed the test to use an explicit executor, but forgot to remove the queue. That allowed the loader to submit all the entries to the executor before the test's task called {{TaskContext.stop()}}. > PreloadingWithWriteBehindTest.testIfCanLoadKeysConcurrently random failures > --------------------------------------------------------------------------- > > Key: ISPN-6445 > URL: https://issues.jboss.org/browse/ISPN-6445 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1, 9.0.0.Final > > > The test assumes that the {{AdvancedAsyncCacheLoader.size()}} is accurate, but the implementation actually ignores the in-memory changes and just delegates to the real loader's {{size()}}. > Also, the method doesn't really belong in this test, because it doesn't use preloading. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016