June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1896) ClusteredGetCommands should never fail with a SuspectException

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-1896?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-1896: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > ClusteredGetCommands should never fail with a SuspectException > -------------------------------------------------------------- > > Key: ISPN-1896 > URL: https://issues.jboss.org/browse/ISPN-1896 > Project: Infinispan > Issue Type: Bug > Components: RPC > Affects Versions: 5.1.6.FINAL > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 6.0.0.Alpha1 > > > I have seen this exception in the core test suite logs: > {noformat} > 2012-03-02 15:07:19,718 ERROR (testng-VersionedDistStateTransferTest) [org.infinispan.test.fwk.UnitTestTestNGListener] Method testStateTransfer(org.infinispan.container.versioning.VersionedDistStateTransferTest) threw an exceptionorg.infinispan.CacheException: SuspectedException > at org.infinispan.util.Util.rewrapAsCacheException(Util.java:524) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:168) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:478) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:148) > at org.infinispan.distribution.DistributionManagerImpl.retrieveFromRemoteSource(DistributionManagerImpl.java:169) > at org.infinispan.interceptors.DistributionInterceptor.realRemoteGet(DistributionInterceptor.java:212) > at org.infinispan.interceptors.DistributionInterceptor.remoteGetAndStoreInL1(DistributionInterceptor.java:194) > at org.infinispan.interceptors.DistributionInterceptor.remoteGetBeforeWrite(DistributionInterceptor.java:440) > at org.infinispan.interceptors.DistributionInterceptor.handleWriteCommand(DistributionInterceptor.java:455) > at org.infinispan.interceptors.DistributionInterceptor.visitPutKeyValueCommand(DistributionInterceptor.java:274) > ... > Caused by: SuspectedException > at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:349) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:263) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:163) > ... 60 more > {noformat} > The remote get command should return null instead of failing, even if it had a single target node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2162) ParallelCacheStartTest.testParallelStartup fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2162?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2162: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > ParallelCacheStartTest.testParallelStartup fails randomly > --------------------------------------------------------- > > Key: ISPN-2162 > URL: https://issues.jboss.org/browse/ISPN-2162 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Galder Zamarreño > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1 > > > Failed tests: testParallelStartup(org.infinispan.api.ParallelCacheStartTest): Timed out before caches had complete views. Expected 1 members in each view. Views are as follows: [[ParallelCacheStartTest-NodeA-41416, ParallelCacheStartTest-NodeB-21482]] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2161) InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2161?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2161: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > InitiatorCrashPessimisticReplTest.testInitiatorNodeCrashesBeforeCommit fails randomly > ------------------------------------------------------------------------------------- > > Key: ISPN-2161 > URL: https://issues.jboss.org/browse/ISPN-2161 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1 > > Attachments: testInitiatorNodeCrashesBeforeCommit-0.log > > > Failed tests: testInitiatorNodeCrashesBeforeCommit(org.infinispan.lock.singlelock.replicated.pessimistic.InitiatorCrashPessimisticReplTest): expected key 'k' to be locked on cache Cache '___defaultcache'@InitiatorCrashPessimisticReplTest-NodeD-44283, but it is not -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2160) ReplWriteSkewTest.testSharedCounter failing randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2160?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2160: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > ReplWriteSkewTest.testSharedCounter failing randomly > ---------------------------------------------------- > > Key: ISPN-2160 > URL: https://issues.jboss.org/browse/ISPN-2160 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1 > > > Failing randomly with: > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.ReplWriteSkewTest): > Node-2 has put a duplicate value{code} > TRACE logs coming right up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2115) Relative path in rhq ant task cause build to fail

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2115?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2115: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Relative path in rhq ant task cause build to fail > ------------------------------------------------- > > Key: ISPN-2115 > URL: https://issues.jboss.org/browse/ISPN-2115 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Thomas Fromm > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > When the directory ../../ above the infinispan source dir is not writable, > than build fails: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project infinispan-rhq-plugin: An Ant BuildException has occured: Directory /usr/local/inubit/jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins creation was not successful for an unknown reason > [ERROR] around Ant part ...<mkdir dir="../../..//jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins"/>... @ 4:116 in /usr/local/inubit/tf/infinispan/rhq-plugin/target/antrun/build-main.xml > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project infinispan-rhq-plugin: An Ant BuildException has occured: Directory /usr/local/inubit/jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins creation was not successful for an unknown reason > In current case the /usr/local/inubit/ is not writable for the user. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2143) Improve how different indexed caches sync up on new indexed types

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2143?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2143: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Improve how different indexed caches sync up on new indexed types > ----------------------------------------------------------------- > > Key: ISPN-2143 > URL: https://issues.jboss.org/browse/ISPN-2143 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > Currently when a node receives an unknown type, it doesn't inform all other nodes, which might fail to get metadata and index boot information from it. > Also, the list of known types should be stored somewhere. > When a shared index is used, we might be able to load some type names from the index itself, but unfortunately usually we need the type name to initialize the index. Rely on an index storage convention? > See also comments in {{org.infinispan.query.indexmanager.IndexUpdateCommand}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2272) Migrate deprecated configuration API in tests infinispan-core

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2272?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2272: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Migrate deprecated configuration API in tests infinispan-core > ------------------------------------------------------------- > > Key: ISPN-2272 > URL: https://issues.jboss.org/browse/ISPN-2272 > Project: Infinispan > Issue Type: Sub-task > Components: Test Suite > Affects Versions: 5.2.0.Alpha3 > Reporter: Thomas Fromm > Assignee: Navin Surtani > Fix For: 6.0.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2264) DistL1WriteSkewTest.testSharedCounter failing randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2264?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2264: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > DistL1WriteSkewTest.testSharedCounter failing randomly > ------------------------------------------------------ > > Key: ISPN-2264 > URL: https://issues.jboss.org/browse/ISPN-2264 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1 > > > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.DistL1WriteSkewTest): > Timed out waiting for updater threads{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2250) Handle all the remaining review comments for the NBST pull reques

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2250?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2250: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Handle all the remaining review comments for the NBST pull reques > ----------------------------------------------------------------- > > Key: ISPN-2250 > URL: https://issues.jboss.org/browse/ISPN-2250 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Alpha3 > Reporter: Mircea Markus > Assignee: Adrian Nistor > Fix For: 6.0.0.Alpha1 > > > These are still visible even after the pull request is closed. > Dan, please don't delete the t_nbst branch before handling these as we might loose them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2240) Per-key lock container leads to superfluous TimeoutExceptions on concurrent access to same key

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2240?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2240: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Per-key lock container leads to superfluous TimeoutExceptions on concurrent access to same key > ---------------------------------------------------------------------------------------------- > > Key: ISPN-2240 > URL: https://issues.jboss.org/browse/ISPN-2240 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency > Affects Versions: 5.1.6.FINAL, 5.1.x > Reporter: Robert Stupp > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha1 > > Attachments: ISPN-2240_fix_TimeoutExceptions.patch, somehow.zip > > > Hi, > I've encountered a lot of TimeoutExceptions just running a load test against an infinispan cluster. > I tracked down the reason and found out, that the code in org.infinispan.util.concurrent.locks.containers.AbstractPerEntryLockContainer#releaseLock() causes these superfluous TimeoutExceptions. > A small test case (which just prints out timeouts, too late timeouts and "paints" a lot of dots to the console - more dots/second on the console means better throughput ;-) > In a short test I extended the class ReentrantPerEntryLockContainer and changed the implementation of releaseLock() as follows: > {noformat} > public void releaseLock(Object lockOwner, Object key) { > ReentrantLock l = locks.get(key); > if (l != null) { > if (!l.isHeldByCurrentThread()) > throw new IllegalStateException("Lock for [" + key + "] not held by current thread " + Thread.currentThread()); > while (l.isHeldByCurrentThread()) > unlock(l, lockOwner); > if (!l.hasQueuedThreads()) > locks.remove(key); > } > else > throw new IllegalStateException("No lock for [" + key + ']'); > } > {noformat} > The main improvement is that locks are not removed from the concurrent map as long as other threads are waiting on that lock. > If the lock is removed from the map while other threads are waiting for it, they may run into timeouts and force TimeoutExceptions to the client. > The above methods "paints more dots per second" - means: it gives a better throughput for concurrent accesses to the same key. > The re-implemented method should also fix some replication timeout exceptions. > Please, please add this to 5.1.7, if possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

9 years, 7 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013