February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6279) Refactor CacheLoader API to make it thread safe

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6279: ----------------------------------------- Summary: Refactor CacheLoader API to make it thread safe Key: ISPN-6279 URL: https://issues.jboss.org/browse/ISPN-6279 Project: Infinispan Issue Type: Feature Request Reporter: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6276) Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6276?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-6276: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1312186|https://bugzilla.redhat.com/show_bug.cgi?id=1312186] from NEW to ASSIGNED > Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader > ---------------------------------------------------------- > > Key: ISPN-6276 > URL: https://issues.jboss.org/browse/ISPN-6276 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Sebastian Łaskawiec > > org.infinispan.persistence.async.AdvancedAsyncCacheLoader$process creates a HashSet, and passes it to loadAllKeys(). > loadAllKeys() creates a task to get each key and add it to the HashSet. > This task is run by org.infinispan.persistence.file.SingleFileStore#process, which runs it in multiple threads at once (one thread per key). > There is no synchronization on that HashSet that is shared by the multiple threads. > HashSet is not thread safe. One known side effect of non-synchronized access by multiple threads is infinite loops, which has been witnessed here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6278) Security documentation for ISPN server is outdated

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6278?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6278: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4040 > Security documentation for ISPN server is outdated > -------------------------------------------------- > > Key: ISPN-6278 > URL: https://issues.jboss.org/browse/ISPN-6278 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Servers > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > [Security setup|http://infinispan.org/docs/8.2.x/infinispan_server_guide/infinispan...] is outdated, {{mapper}} parameter is not supported any more. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6278) Security documentation for ISPN server is outdated

by Vojtech Juranek (JIRA)

[ https://issues.jboss.org/browse/ISPN-6278?page=com.atlassian.jira.plugin.... ] Vojtech Juranek updated ISPN-6278: ---------------------------------- Status: Open (was: New) > Security documentation for ISPN server is outdated > -------------------------------------------------- > > Key: ISPN-6278 > URL: https://issues.jboss.org/browse/ISPN-6278 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Servers > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > > [Security setup|http://infinispan.org/docs/8.2.x/infinispan_server_guide/infinispan...] is outdated, {{mapper}} parameter is not supported any more. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6278) Security documentation for ISPN server is outdated

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-6278: ------------------------------------- Summary: Security documentation for ISPN server is outdated Key: ISPN-6278 URL: https://issues.jboss.org/browse/ISPN-6278 Project: Infinispan Issue Type: Bug Components: Documentation-Servers Reporter: Vojtech Juranek Assignee: Vojtech Juranek [Security setup|http://infinispan.org/docs/8.2.x/infinispan_server_guide/infinispan...] is outdated, {{mapper}} parameter is not supported any more. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6082) Management console - cluster view page doesn't count nodes that are offline in #nodes #hosts column

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6082?page=com.atlassian.jira.plugin.... ] Roman Macor resolved ISPN-6082. ------------------------------- Resolution: Done Node and host count is displayed correctly. > Management console - cluster view page doesn't count nodes that are offline in #nodes #hosts column > --------------------------------------------------------------------------------------------------- > > Key: ISPN-6082 > URL: https://issues.jboss.org/browse/ISPN-6082 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > page: Clusters tab > Count of nodes and hosts only counts nodes that are running. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6277) Avoid NullPointerException errors in the core test suite logs

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6277: ---------------------------------- Summary: Avoid NullPointerException errors in the core test suite logs Key: ISPN-6277 URL: https://issues.jboss.org/browse/ISPN-6277 Project: Infinispan Issue Type: Task Components: Test Suite - Core Affects Versions: 8.2.0.Beta2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.CR1 Some tests log {{NullPointerException}}-caused error messages when they pass, which makes it hard to tell if it's a real problem or not. {{CacheManagerTest}}: cluster executor tests throw {{NullPointerException}} explicitly. {noformat} 11:20:04,030 WARN (remote-thread-CacheManagerTest-NodeN-p1091-t1:) [GlobalInboundInvocationHandler] ISPN000071: Caught exception when handling command org.infinispan.manager.impl.ReplicableCommandRunnable@6c20c6c7 java.lang.NullPointerException at org.infinispan.manager.CacheManagerTest$13.lambda$call$81c80a4a$1(CacheManagerTest.java:594) ~[test-classes/:?] at org.infinispan.manager.impl.ReplicableCommandRunnable.perform(ReplicableCommandRunnable.java:33) ~[classes/:?] at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler$2.run(GlobalInboundInvocationHandler.java:158) [classes/:?] at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:199) [classes/:?] {noformat} Various tests, during cluster shutdown: an incoming {{CacheTopologyControlCommand}} can re-create the {{ClusterTopologyManager}} component, and call {{handleRebalanceCompleted()}} without {{start()}}. {noformat} 11:21:24,637 WARN (remote-thread-NumOwnersNodeStopInSequenceTest-NodeY-p8288-t6:) [CacheTopologyControlCommand] ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=___defaultcache, type=REBALANCE_CONFIRM, sender=NumOwnersNodeStopInSequenceTest-NodeAB-56593, joinInfo=null, topologyId=9, rebalanceId=0, currentCH=null, pendingCH=null, availabilityMode=null, actualMembers=null, throwable=null, viewId=3} java.lang.NullPointerException at org.infinispan.topology.ClusterTopologyManagerImpl.handleRebalanceCompleted(ClusterTopologyManagerImpl.java:219) ~[classes/:?] at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:176) ~[classes/:?] at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:153) [classes/:?] at org.infinispan.remoting.inboundhandler.GlobalInboundInvocationHandler$2.run(GlobalInboundInvocationHandler.java:158) [classes/:?] at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:199) [classes/:?] {noformat} {{InitialClusterSizeTest}}: stops the cache manager after if failed to start, and {{DefaultCacheManager.stop()}} throws an exception because the internal cache registry was not registered. {noformat} 11:21:29,827 WARN (testng-InitialClusterSizeTest:) [TestingUtil] Problems killing cache manager org.infinispan.manager.DefaultCacheManager@1d9fdcf9@Address:null java.lang.NullPointerException at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:684) ~[classes/:?] at org.infinispan.test.TestingUtil.killCacheManagers(TestingUtil.java:643) [test-classes/:?] at org.infinispan.test.MultipleCacheManagersTest.clearContent(MultipleCacheManagersTest.java:101) [test-classes/:?] {noformat} {{DistributedExecutorTest}}: {{testCancelAndGet}} uses a {{LongRunningCallable}}, but never registers the barrier it needs in the cache. {noformat} 11:22:41,320 WARN (remote-thread-ReplSyncDistributedExecutorTest-NodeX-p15029-t5:) [NonTotalOrderPerCacheInboundInvocationHandler] ISPN000071: Caught exception when handling command DistributedExecuteCommand [cache=Cache 'DistributedExecutorTest-REPL_SYNC'@ReplSyncDistributedExecutorTest-NodeX-55556, keys=[], callable=org.infinispan.distexec.DistributedExecutorTest$LongRunningCallable@78655960] java.lang.NullPointerException at org.infinispan.distexec.DistributedExecutorTest$LongRunningCallable.call(DistributedExecutorTest.java:346) ~[test-classes/:?] at org.infinispan.distexec.DistributedExecutorTest$LongRunningCallable.call(DistributedExecutorTest.java:331) ~[test-classes/:?] at org.infinispan.commands.read.DistributedExecuteCommand.perform(DistributedExecuteCommand.java:107) ~[classes/:?] at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokePerform(BasePerCacheInboundInvocationHandler.java:92) [classes/:?] at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:34) [classes/:?] {noformat} {{NonTxStateTransferOverwritingValue2Test}}: {{ClusteringDependentLogicDelegator.commitEntry()}} doesn't handle {{ClearCacheEntry}} correctly (used for {{ClearCommand}}). {noformat} 11:27:16,565 ERROR (remote-thread-NonTxStateTransferOverwritingValue2Test-NodeB-p39829-t5:) [InvocationContextInterceptor] ISPN000136: Error executing command ClearCommand, writing keys [] java.lang.NullPointerException at org.infinispan.commons.hash.MurmurHash3.hash(MurmurHash3.java:397) ~[infinispan-commons-8.2.0-SNAPSHOT.jar:8.2.0-SNAPSHOT] at org.infinispan.distribution.ch.impl.HashFunctionPartitioner.getSegment(HashFunctionPartitioner.java:51) ~[classes/:?] at org.infinispan.distribution.group.PartitionerConsistentHash.getSegment(PartitionerConsistentHash.java:47) ~[classes/:?] at org.infinispan.distribution.group.PartitionerConsistentHash.isKeyLocalToNode(PartitionerConsistentHash.java:87) ~[classes/:?] at org.infinispan.distribution.impl.DistributionManagerImpl.getLocality(DistributionManagerImpl.java:71) ~[classes/:?] at org.infinispan.interceptors.locking.ClusteringDependentLogic$DistributionLogic.localNodeIsOwner(ClusteringDependentLogic.java:469) ~[classes/:?] at org.infinispan.interceptors.locking.ClusteringDependentLogic$DistributionLogic.commitSingleEntry(ClusteringDependentLogic.java:500) ~[classes/:?] at org.infinispan.interceptors.locking.ClusteringDependentLogic$AbstractClusteringDependentLogic.commitEntry(ClusteringDependentLogic.java:115) ~[classes/:?] at org.infinispan.test.fwk.ClusteringDependentLogicDelegator.commitEntry(ClusteringDependentLogicDelegator.java:49) ~[test-classes/:?] at org.infinispan.distribution.rehash.NonTxStateTransferOverwritingValue2Test$3.commitEntry(NonTxStateTransferOverwritingValue2Test.java:212) ~[test-classes/:?] at org.infinispan.interceptors.EntryWrappingInterceptor.commitContextEntry(EntryWrappingInterceptor.java:479) ~[classes/:?] at org.infinispan.interceptors.EntryWrappingInterceptor.commitEntryIfNeeded(EntryWrappingInterceptor.java:655) ~[classes/:?] at org.infinispan.interceptors.EntryWrappingInterceptor.commitContextEntries(EntryWrappingInterceptor.java:465) ~[classes/:?] {noformat} {{StateResponseOrderingTest}}: test was calling {{PerCacheInboundInvocationHandler.handle(command)}} without first calling {{StateResponseCommand.init()}} {noformat} 11:27:18,781 WARN (testng-StateResponseOrderingTest:) [NonTotalOrderTxPerCacheInboundInvocationHandler] ISPN000071: Caught exception when handling command StateResponseCommand{cache=___defaultcache, stateChunks=[StateChunk{segmentId=0, cacheEntries=1, isLastChunk=true}, StateChunk{segmentId=1, cacheEntries=1, isLastChunk=true}], origin=StateResponseOrderingTest-NodeD-39668, topologyId=6} java.lang.NullPointerException at org.infinispan.statetransfer.StateResponseCommand.perform(StateResponseCommand.java:67) ~[classes/:?] at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.invokePerform(BasePerCacheInboundInvocationHandler.java:92) [classes/:?] at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:34) [classes/:?] at org.infinispan.remoting.inboundhandler.BasePerCacheInboundInvocationHandler.handleRunnable(BasePerCacheInboundInvocationHandler.java:132) [classes/:?] at org.infinispan.remoting.inboundhandler.NonTotalOrderTxPerCacheInboundInvocationHandler.handle(NonTotalOrderTxPerCacheInboundInvocationHandler.java:99) [classes/:?] at org.infinispan.distribution.rehash.StateResponseOrderingTest.testSimulatedOldStateResponse(StateResponseOrderingTest.java:113) [test-classes/:?] {noformat} {{ParserOverrideTest}}, {{XmlFileParsingTest}}: {{ClusterTopologyManagerImpl}} view handler can execute after {{JGroupsTransport}} was stopped and {{dispatcher}} was set to {{null}}. {noformat} 11:25:46,357 WARN (transport-thread-ParserOverrideTest-NodeA-p30089-t1:) [ClusterTopologyManagerImpl] ISPN000197: Error updating cluster member list java.lang.NullPointerException at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotelyAsync(JGroupsTransport.java:612) ~[classes/:?] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:533) ~[classes/:?] at org.infinispan.topology.ClusterTopologyManagerImpl.confirmMembersAvailable(ClusterTopologyManagerImpl.java:444) ~[classes/:?] at org.infinispan.topology.ClusterTopologyManagerImpl.updateCacheMembers(ClusterTopologyManagerImpl.java:431) ~[classes/:?] at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:354) ~[classes/:?] at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$0(ClusterTopologyManagerImpl.java:132) ~[classes/:?] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_74] at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173) [classes/:?] at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151) [classes/:?] {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6276) Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6276?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6276: -------------------------------------- Status: Open (was: New) > Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader > ---------------------------------------------------------- > > Key: ISPN-6276 > URL: https://issues.jboss.org/browse/ISPN-6276 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Sebastian Łaskawiec > > org.infinispan.persistence.async.AdvancedAsyncCacheLoader$process creates a HashSet, and passes it to loadAllKeys(). > loadAllKeys() creates a task to get each key and add it to the HashSet. > This task is run by org.infinispan.persistence.file.SingleFileStore#process, which runs it in multiple threads at once (one thread per key). > There is no synchronization on that HashSet that is shared by the multiple threads. > HashSet is not thread safe. One known side effect of non-synchronized access by multiple threads is infinite loops, which has been witnessed here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6276) Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6276?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6276: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4047 > Non-threadsafe use of HashSet in AdvancedAsyncCacheLoader > ---------------------------------------------------------- > > Key: ISPN-6276 > URL: https://issues.jboss.org/browse/ISPN-6276 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Sebastian Łaskawiec > > org.infinispan.persistence.async.AdvancedAsyncCacheLoader$process creates a HashSet, and passes it to loadAllKeys(). > loadAllKeys() creates a task to get each key and add it to the HashSet. > This task is run by org.infinispan.persistence.file.SingleFileStore#process, which runs it in multiple threads at once (one thread per key). > There is no synchronization on that HashSet that is shared by the multiple threads. > HashSet is not thread safe. One known side effect of non-synchronized access by multiple threads is infinite loops, which has been witnessed here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6080) Management console - cluster view page displays offline nodes from other clusters

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6080?page=com.atlassian.jira.plugin.... ] Roman Macor resolved ISPN-6080. ------------------------------- Resolution: Done Nodes are displayed correctly. > Management console - cluster view page displays offline nodes from other clusters > --------------------------------------------------------------------------------- > > Key: ISPN-6080 > URL: https://issues.jboss.org/browse/ISPN-6080 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Go to Clusters -> Make sure one cluster is stopped, the other is started -> go to started cluster > Result: Nodes from started cluster are displayed as well as nodes from stopped cluster. > Expected result: Only nodes from started cluster should be displayed in "started" cluster page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016