October 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1822) Cache entry not evicted from memory on IBM JDK when another entry was loaded from a cache loader and maxEntries had been reached

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1822?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1822: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > Cache entry not evicted from memory on IBM JDK when another entry was loaded from a cache loader and maxEntries had been reached > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-1822 > URL: https://issues.jboss.org/browse/ISPN-1822 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 5.1.0.FINAL > Environment: java version "1.6.0" > Java(TM) SE Runtime Environment (build pxi3260sr9fp1-20110208_03(SR9 FP1)) > IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110203_74623 (JIT enabled, AOT enabled) ; > java version "1.7.0" > Java(TM) SE Runtime Environment (build pxi3270-20110827_01) > IBM J9 VM (build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604 (JIT enabled, AOT enabled) > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > This behavior is specific to IBM JDK (I tried JDK6 and 7), it works fine with Java HotSpot. > Steps to reproduce the problem: > 1) set maxEntries for eviction to 2 and algorithm e.g. to LRU > 2) store 3 entries key1, key2, key3 to the cache (after that you can see that the cache contains only 2 entries - key2 and key3, the first one was evicted from memory) > 3) call cache.get("key1") > 4) PROBLEM - cache contains all key1, key2, key3 even though it should contain only 2 entries - only happens with IBM JDK (6 or 7 ..no matter) > I'll shortly issue a pull request with a test to ispn-core -- 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

12 years, 6 months

1
0
0 / 0

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

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1790?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1790: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > Release script should not rip off comments from POM.XML files > ------------------------------------------------------------- > > Key: ISPN-1790 > URL: https://issues.jboss.org/browse/ISPN-1790 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Affects Versions: 5.1.0.FINAL > Reporter: Sanne Grinovero > Assignee: Manik Surtani > Priority: Minor > Labels: release.py > Fix For: 6.0.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 For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1548) Refactor API and Commons in self-contained packages to avoid package splitting issues

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1548?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1548: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > Refactor API and Commons in self-contained packages to avoid package splitting issues > ------------------------------------------------------------------------------------- > > Key: ISPN-1548 > URL: https://issues.jboss.org/browse/ISPN-1548 > Project: Infinispan > Issue Type: Task > Components: Core API > Affects Versions: 5.1.0.BETA5 > Reporter: NadirX > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > With the split of core into api and commons (ISPN-1490) we have caused split packages (i.e. classes in the same package are split across multiple jars). This causes problems with OSGi (ISPN-1537) and will also be disallowed when signed jars will be made compulsory in EAP. > We therefore need to introduce new packages explicitly for api and commons. This will obviously have some impact on client 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1368) RpcManagerFactory should not create an RpcManager for local caches

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1368?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1368: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > RpcManagerFactory should not create an RpcManager for local caches > ------------------------------------------------------------------ > > Key: ISPN-1368 > URL: https://issues.jboss.org/browse/ISPN-1368 > Project: Infinispan > Issue Type: Bug > Components: RPC > Affects Versions: 5.0.0.FINAL > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 6.0.0.Final > > > As indicated in ISPN-1348, RpcManagerFactory should not create an RpcManager for those caches whose mode is LOCAL,, even if the transport is not null. > Btw, I don't want this fixed till ISPN-1366 is in place, otherwise ISPN-1348 does become a problem and finding a solution for it without ISPN-1366 complicates things greatly. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1146) Improve documentation around transaction and locking

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1146?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1146: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > Improve documentation around transaction and locking > ---------------------------------------------------- > > Key: ISPN-1146 > URL: https://issues.jboss.org/browse/ISPN-1146 > Project: Infinispan > Issue Type: Task > Components: Transactions > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Final > > > As suggested by Jonathan Halliday: > - preserving some subset of the existing transactional guarantees is all well and good BUT if the user is relying on additional 'guarantees' that are not preserved in all cases then they'll be in trouble. Therefore, it's essential to document not just what the minimum expected guarantees for a given config are, but also that no additional properties that may coincidently be observed are actually guaranteed. Some vendors go further and explicitly document the bad things that may happen with given settings, since in some cases these are not easy to reproduce in testing. -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2059) Custom CacheLoaders are treated as CacheStores unless annotated with @CacheLoaderMetadata

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-2059?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-2059: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > Custom CacheLoaders are treated as CacheStores unless annotated with @CacheLoaderMetadata > ----------------------------------------------------------------------------------------- > > Key: ISPN-2059 > URL: https://issues.jboss.org/browse/ISPN-2059 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.1.6.FINAL > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > If the @CacheLoaderMetadata is missing, Infinispan will treat the CacheLoader as a CacheStore: if it's not implementing CacheStore as well the component will fail. > @CacheLoaderMetadata should be optional. -- 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

12 years, 6 months

1
0
0 / 0

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

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-2016?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-2016: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > 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: NadirX > Assignee: Manik Surtani > Priority: Minor > Fix For: 6.0.0.Final > > -- 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1952) Use RESTEasy's HTTP frontend for the REST server

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1952?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1952: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > Use RESTEasy's HTTP frontend for the REST server > ------------------------------------------------ > > Key: ISPN-1952 > URL: https://issues.jboss.org/browse/ISPN-1952 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: NadirX > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Using RESTEasy's HTTP frontend would allow the following: > - allow starting of a containerless REST Server using the startServer.sh script in the distibution > - drop the need for JBossWeb in JDG > - Give us some noticeable performance improvements -- 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

12 years, 6 months

1
0
0 / 0

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

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1896?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1896: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > 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.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 For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

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

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-1947: -------------------------------- Fix Version/s: 6.0.0.Final (was: 6.0.0.CR1) > 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: 6.0.0.Final > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2013