April 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1345) Dirty reads may occurs on mutable objects

by Christophe Labouisse (JIRA)

Dirty reads may occurs on mutable objects ----------------------------------------- Key: ISPN-1345 URL: https://issues.jboss.org/browse/ISPN-1345 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.0.0.FINAL Environment: Windows Java 1.6.0_26 Reporter: Christophe Labouisse Assignee: Manik Surtani In local mode, I create a cache like this: {code} cacheManager = new DefaultCacheManager(); cacheManager.getDefaultConfiguration().fluent().storeAsBinary().transaction().cacheStopTimeout(5000); final Configuration config = new Configuration().fluent().transactionManagerLookup(this.tmLookup).locking() .isolationLevel(IsolationLevel.READ_COMMITED).build(); this.cacheManager.defineConfiguration("Gruik", config); this.cache = this.cacheManager.getCache("Gruik"); {code} When retrieving data using {{cache.get(_key_)}} I find out that Infinispan returns the object instance actually stored in the cache datastore. This is OK when the inserted objects are immutable but fails to achieve isolation when using mutable objects. For instance on a simple Pojo with a {{get/setValue}}. ||Step||Reader||Writer|| |1|Starts transaction| | |2|{{value = cache.get(KEY);}}| | |3|{{System.out.println(value.getValue());}} Prints 42| | |4| |Starts transaction| |5| |{{value = cache.get(KEY);}} Same instance than step 2| |6| |{{value.setValue(666); // Prepare update}}| |7|{{System.out.println(value.getValue());}} Prints 666 !| | |8|{{value = cache.get(KEY);}} Same instance than step 2| | |9| |{{cache.put(KEY,value);}}| |10| |Commits transaction| |11|{{value = cache.get(KEY);}} Same instance than step 2| | |12|{{System.out.println(value.getValue());}} Prints 666| | |13|Commits transaction| | According to the READ_COMMITTED specification, the value returned printed on step 7 should be 42, as the setting to 666 is not committed yes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

8
18
0 / 0

[JBoss JIRA] Created: (ISPN-1272) Move away from javadoc's aggregate goal

by Galder Zamarreño (JIRA)

Move away from javadoc's aggregate goal --------------------------------------- Key: ISPN-1272 URL: https://issues.jboss.org/browse/ISPN-1272 Project: Infinispan Issue Type: Enhancement Components: Build process Reporter: Galder Zamarreño Assignee: Manik Surtani Priority: Minor Fix For: 5.2.0.FINAL We should move away from maven javadoc's aggregate goal because it creates a lot of pains. For starters, it often spawns a separate process, -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-1213) TreeCache expires parents that have children

by Todd Ciezadlo (JIRA)

TreeCache expires parents that have children -------------------------------------------- Key: ISPN-1213 URL: https://issues.jboss.org/browse/ISPN-1213 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 4.2.1.FINAL Reporter: Todd Ciezadlo Assignee: Manik Surtani TreeCache parents expire according to the max-idle value even if they contain children. This puts the tree cache in an inconsistent state since the "dangling" children can be retrieved through TreeCache.get(FQN, String) calls, but cannot be traversed to through TreeCache.getRoot() and Node.getChildren() calls. Copied a unit test to Steps to Reproduce. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
16
0 / 0

[JBoss JIRA] Created: (ISPN-959) Refactor documentation on wiki

by Manik Surtani (JIRA)

Refactor documentation on wiki ------------------------------ Key: ISPN-959 URL: https://issues.jboss.org/browse/ISPN-959 Project: Infinispan Issue Type: Task Affects Versions: 5.0.0.Final Reporter: Manik Surtani Assignee: Manik Surtani This would take into account the new Confluence setup on docs.jboss.org, as well as docbook exporters and the ability to organise documentation as well as wiki pages based on versions of Infinispan. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1790) Release script should not rip off comments from XML files

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1790: ------------------------------------- Summary: Release script should not rip off comments from XML files Key: ISPN-1790 URL: https://issues.jboss.org/browse/ISPN-1790 Project: Infinispan Issue Type: Bug Components: Build process Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.1.0.FINAL Comparing the git commit which was used to release 5.1.0.Final to the final tag of the released version, reveals some changes which are likely unintended: * All Copyright statements removed * All comments removed (useful and unuseful) * In some way changed the inlined scripts for Google analytics - not sure if it's still working -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
4
0 / 0

[JBoss JIRA] (ISPN-2016) Release script should push branch to origin after updating to version+1

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2016: ------------------------------------- Summary: Release script should push branch to origin after updating to version+1 Key: ISPN-2016 URL: https://issues.jboss.org/browse/ISPN-2016 Project: Infinispan Issue Type: Bug Components: Build process Affects Versions: 5.1.4.FINAL Reporter: Tristan Tarrant Assignee: Manik Surtani Priority: Minor Fix For: 5.2.0.FINAL -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
1
0 / 0

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1947: ------------------------------------- Summary: Automate staging repository step in release script Key: ISPN-1947 URL: https://issues.jboss.org/browse/ISPN-1947 Project: Infinispan Issue Type: Task Components: Build process Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Optional Fix For: 5.2.0.ALPHA1 The following plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) {code:xml} <plugin> <groupId>org.sonatype.plugins</groupId> <artifactId>nexus-maven-plugin</artifactId> <configuration> <nexusUrl>https://repository.jboss.org/nexus</nexusUrl> <automatic>true</automatic> </configuration> </plugin> {code} Goals are described at: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plu... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-761) Cache.keySet(), entrySet(), values(), size() ignore contents of cache loader

by Paul Ferraro (JIRA)

Cache.keySet(),entrySet(),values(),size() ignore contents of cache loader ------------------------------------------------------------------------- Key: ISPN-761 URL: https://jira.jboss.org/browse/ISPN-761 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.0.BETA1 Reporter: Paul Ferraro Assignee: Manik Surtani Passivated cache entries are not represented in values returned by the keySet(), entrySet(), values(), and size() Cache methods. This results in inconsistent behavior, since it is possible that a given cache key may not be contained in keySet() even though Cache.get(...) would return a non-null value if the entry was previously passivated. I think CacheLoaderInterceptor needs to implement the following methods: Object visitSizeCommand(InvocationContext ctx, SizeCommand command) throws Throwable Object visitValuesCommand(InvocationContext ctx, ValuesCommand command) throws Throwable Object visitEntrySetCommand(InvocationContext ctx, EntrySetCommand command) throws Throwable Object visitKeySetCommand(InvocationContext ctx, KeySetCommand command) throws Throwable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
14
0 / 0

[JBoss JIRA] (ISPN-1951) Use MERGE3 in the default UDP configuration

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1951: ---------------------------------- Summary: Use MERGE3 in the default UDP configuration Key: ISPN-1951 URL: https://issues.jboss.org/browse/ISPN-1951 Project: Infinispan Issue Type: Task Components: Configuration Affects Versions: 5.1.3.CR1, 5.1.2.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 5.1.3.FINAL, 5.2.0.ALPHA1 Bela recommends using MERGE3 instead of MERGE2 in UDP clusters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
9
0 / 0

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

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1896: ---------------------------------- Summary: 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.2.CR1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.1.2.FINAL 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2012