July 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1279) Update links in documentation to point to 5.0 version of API docs

by Martin Gencur (JIRA)

Update links in documentation to point to 5.0 version of API docs ----------------------------------------------------------------- Key: ISPN-1279 URL: https://issues.jboss.org/browse/ISPN-1279 Project: Infinispan Issue Type: Task Reporter: Martin Gencur Assignee: Pete Muir Documents at https://docs.jboss.org/author/display/ISPN (user guide, tutorials, etc.) should point (via links) to newer API documentation (http://docs.jboss.org/infinispan/5.0/apidocs/). Now they point to 4.0 API docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-1258) IllegalMonitorStateException when prepare/commit sequence happens in diff threads

by Galder Zamarreño (JIRA)

IllegalMonitorStateException when prepare/commit sequence happens in diff threads --------------------------------------------------------------------------------- Key: ISPN-1258 URL: https://issues.jboss.org/browse/ISPN-1258 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.0.0.CR8 Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.0.0.FINAL There's no guarantees at the JGroups level that in a sequence of prepare+commit calls, both will be handled by the same thread as shown in the logs: Here's a prepare call: {code}2011-07-20 21:01:44,400 2011 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (OOB-1,Infinispan-Cluster,NodeB-10116:) Attempting to execute command: PrepareCommand {gtx=GlobalTransaction:<NodeA-32281>:1:local, modifications=[PutKeyValueCommand{key=a, value=value1, flags=null, putIfAbsent=false, lifespanMillis=-1, maxIdleTimeMillis=-1}], onePhaseCommit=false, gtx=GlobalTransaction:<NodeA-32281>:1:local, cacheName='cache1'} [sender=NodeA-32281] ... 2011-07-20 21:01:44,404 2015 TRACE [org.infinispan.util.concurrent.locks.containers.AbstractPerEntryLockContainer] (OOB-1,Infinispan-Cluster,NodeB-10116:cache1) Acquired lock java.util.concurrent.locks.ReentrantLock@7cd1a1ab[Locked by thread OOB-1,Infinispan-Cluster,NodeB-10116]{code} And the commit: {code}2011-07-20 21:01:44,418 2029 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (OOB-2,Infinispan-Cluster,NodeB-10116:) Attempting to execute command: CommitCommand {gtx=GlobalTransaction:<NodeA-32281>:1:local, cacheName='cache1'} [sender=NodeA-32281] ... 2011-07-20 21:01:44,423 2034 TRACE [org.infinispan.util.concurrent.locks.containers.AbstractPerEntryLockContainer] (OOB-2,Infinispan-Cluster,NodeB-10116:cache1) Unlock lock java.util.concurrent.locks.ReentrantLock@7cd1a1ab[Locked by thread OOB-1,Infinispan-Cluster,NodeB-10116]{code} The end result? {code} 2011-07-20 21:01:44,424 2035 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-2,Infinispan-Cluster,NodeB-10116:cache1) ISPN000136: Execution error java.lang.IllegalMonitorStateException at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:127) at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1239) at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:431) at org.infinispan.util.concurrent.locks.containers.AbstractPerEntryLockContainer.releaseLock(AbstractPerEntryLockContainer.java:113) at org.infinispan.util.concurrent.locks.LockManagerImpl.unlock(LockManagerImpl.java:113) at org.infinispan.interceptors.LockingInterceptor.cleanupLocks(LockingInterceptor.java:375) at org.infinispan.interceptors.LockingInterceptor.visitCommitCommand(LockingInterceptor.java:98) {code} Mircea, could you have a look? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-1269) FileCacheStore contains entries after they have been activated (with passivation enabled)

by Martin Gencur (JIRA)

FileCacheStore contains entries after they have been activated (with passivation enabled) ----------------------------------------------------------------------------------------- Key: ISPN-1269 URL: https://issues.jboss.org/browse/ISPN-1269 Project: Infinispan Issue Type: Bug Components: Eviction, Loaders and Stores Affects Versions: 5.0.0.CR8 Environment: EDG 6 Alpha SNAPSHOT (Infinispan 5 CR8, JBossAS 7.1.0.Alpha1-SNAPSHOT) Reporter: Martin Gencur Assignee: Manik Surtani According to this article: https://docs.jboss.org/author/pages/viewpage.action?pageId=5832809, when passivation is enable along with eviction, entries should exist either in a cache or in a cache store, which is not true with CR8. When an entry is activated (back from the cache store), it still remains in the cache store. Test for this can be found at https://svn.devel.redhat.com/repos/jboss-qa/edg/edg-functional-tests/trun.... In order to run it, one has to set JBOSS_HOME property pointing to an EDG server (I used one with Infinispan CR8 and JBossAS 7.1 SNAPSHOT) and run "mvn clean verify". Configuration files can be found at the above location under src/test/resources dir. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-842) FirstAvailable load balance policy for Hot Rod clients and extend reach of load balance policies

by Galder Zamarreño (JIRA)

FirstAvailable load balance policy for Hot Rod clients and extend reach of load balance policies ------------------------------------------------------------------------------------------------ Key: ISPN-842 URL: https://issues.jboss.org/browse/ISPN-842 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.0.0.BETA1 Create a FirstAvailable load balance policy for Java Hot Rod clients and make sure load balance policies are used by all operations, particularly those extending AbstractKeyOperation. See forum thread for more info. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-1268) Move wakeUpInterval to expiration

by Galder Zamarreño (JIRA)

Move wakeUpInterval to expiration --------------------------------- Key: ISPN-1268 URL: https://issues.jboss.org/browse/ISPN-1268 Project: Infinispan Issue Type: Enhancement Components: Configuration, Eviction Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.FINAL wakeUpInterval only used for eviction, so, move the wakeupInterval attribute from eviction to expiration updating config beans accordingly. Also update the Javadocs: http://docs.jboss.org/infinispan/5.0/apidocs/config.html#ce_default_eviction -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1264) Modify tests to follow Infinispan development guidelines

by Kevin Pollet (JIRA)

Modify tests to follow Infinispan development guidelines -------------------------------------------------------- Key: ISPN-1264 URL: https://issues.jboss.org/browse/ISPN-1264 Project: Infinispan Issue Type: Task Components: CDI integration Affects Versions: 5.0.0.CR8 Reporter: Kevin Pollet Assignee: Kevin Pollet Priority: Minor See https://docs.jboss.org/author/display/ISPN/Contributing+-+The+test+suite -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1257) Invalid warning: lockAcquisitionTimeout > replTimeout, but Infinispan is not clustered

by Tom Waterhouse (JIRA)

Invalid warning: lockAcquisitionTimeout > replTimeout, but Infinispan is not clustered -------------------------------------------------------------------------------------- Key: ISPN-1257 URL: https://issues.jboss.org/browse/ISPN-1257 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.CR8 Reporter: Tom Waterhouse Assignee: Manik Surtani I updated to 5.0.CR8 and received the following warning, even though our infinispan config does not include enablement of clustering: [2011-07-20 13:20:17.742, 21381]WARN [main](TimeoutConfigurationValidatingVisitor.java:67) - ISPN000148: Invalid <locking>:lockAcquisitionTimeout value of 300000. It can not be higher than <sync>:replTimeout which is 15000 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-1260) The default configuration and the default cache manager used by the extension cannot be overridden

by Kevin Pollet (JIRA)

The default configuration and the default cache manager used by the extension cannot be overridden -------------------------------------------------------------------------------------------------- Key: ISPN-1260 URL: https://issues.jboss.org/browse/ISPN-1260 Project: Infinispan Issue Type: Bug Components: CDI integration Affects Versions: 5.0.0.CR8 Reporter: Kevin Pollet Assignee: Kevin Pollet The current mechanism which allows the user to override the default configuration or the default cache manager doesn't work. This is due to WELD-912. One solution might be to use a qualifier provided by the extension. If this qualifier is used on a producer the produced configuration or cache manager will override the default configuration or the default cache manager. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1259) Add package level javadoc

by Kevin Pollet (JIRA)

Add package level javadoc ------------------------- Key: ISPN-1259 URL: https://issues.jboss.org/browse/ISPN-1259 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Priority: Minor -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1212) Improved PING and FD protocols for the testsuite

by Galder Zamarreño (JIRA)

Improved PING and FD protocols for the testsuite ------------------------------------------------ Key: ISPN-1212 URL: https://issues.jboss.org/browse/ISPN-1212 Project: Infinispan Issue Type: Task Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.CR7 Create: - INFINISPAN_TEST_PING: use thread locals to maintain cluster membership since all tests run in same JVM. This would make discovery rock solid and would make the testsuite more robust. - INFINISPAN_TEST_FD: instead of relying on pings to check whether the node is there, attach a cache or cache manager listener to detect when a cache stops or fails and propagate that information back to the membership. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2011