December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3863) JDBC and LevelDB cachestore XSD reference removed lockSupportStore

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3863?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3863: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > JDBC and LevelDB cachestore XSD reference removed lockSupportStore > ------------------------------------------------------------------ > > Key: ISPN-3863 > URL: https://issues.jboss.org/browse/ISPN-3863 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 6.0.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3862) Upgrade JBoss Marshalling to 1.4.x

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3862?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3862: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha1 7.0.0.Final Resolution: Done > Upgrade JBoss Marshalling to 1.4.x > ----------------------------------- > > Key: ISPN-3862 > URL: https://issues.jboss.org/browse/ISPN-3862 > Project: Infinispan > Issue Type: Feature Request > Components: Marshalling > Reporter: Mircea Markus > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > This is needed not only for moving to the latest and greatest, but alto in order to align with Wildfly 8. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3838) L1 entry added by ST when already invalidated

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3838?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-3838: ------------------------------------- I am able to reproduce the issue. Unfortunately updatedkeys is only available while in the middle of State Transfer, so that isn't possible. > L1 entry added by ST when already invalidated > --------------------------------------------- > > Key: ISPN-3838 > URL: https://issues.jboss.org/browse/ISPN-3838 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: William Burns > Priority: Critical > Labels: 620 > > Non-transactional cache with L1 enabled. Node A is losing ownership of an entry, the entry is not removed during ST but is going to L1. > 1. ST builds the invalidation command, EntryWrapping interceptor starts committing all the entries > 2. Write on primary owner (B) occurs > 3. A gets the InvalidateL1Command, removes the ImmortalCacheEntry from data container (as it does not own the entry anymore) > 4. The ST invalidation command commits the MortalCacheEntry with old value, storing it into the data container. > Result: Outdated value is in L1 cache. > As the entry is not locked during the ST, it can be committed as MortalCacheEntry only if it was not changed (removed and possibly then cached again with different value). > (I understand that this wouldn't be easy to implement as the check is not to be executed in perform, but during the actual commit - and atomically in the container.) -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3364) Tests from org.infinispan.atomic package fail with AssertionError

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3364?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-3364: ------------------------------------- Hmm, changing the eviction strategy to LIRS helps only for the Local tests, not for REPL. I.e. LocalDeltaAwarePassivationTest passes on IBM JDK 6 with LIRS but ReplDeltaAwarePassivationTest fails. Maybe the problem is somewhere else. > Tests from org.infinispan.atomic package fail with AssertionError > ----------------------------------------------------------------- > > Key: ISPN-3364 > URL: https://issues.jboss.org/browse/ISPN-3364 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 6.0.0.Alpha1 > Environment: RHEL5_x86, RHEL5_x86_64, RHEL6_x86, RHEL5_x86_64 with IBM JDK7 > Reporter: Vitalii Chepeliuk > Assignee: William Burns > Labels: 620 > Fix For: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Final > > Attachments: LocalDeltaAwarePassivationTest.log.zip, ReplDeltaAwarePassivationTest.log.zip > > > Following tests fail from org.infinispan.atomic package > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testAtomicMap > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testDeltaAware > org.infinispan.atomic.LocalDeltaAwarePassivationTest.testFineGrainedAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testAtomicMap2 > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testDeltaAware > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testDeltaAware2 > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testFineGrainedAtomicMap > org.infinispan.atomic.ReplDeltaAwarePassivationTest.testFineGrainedAtomicMap2 > Add link on jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2255) FineGrainedAtomicMap missing key, value pairs in some cluster nodes in distributed mode, embedded infinispan cache

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2255?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2255: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > FineGrainedAtomicMap missing key,value pairs in some cluster nodes in distributed mode, embedded infinispan cache > ----------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2255 > URL: https://issues.jboss.org/browse/ISPN-2255 > Project: Infinispan > Issue Type: Bug > Components: Fine-grained API > Affects Versions: 5.1.5.FINAL > Environment: Details about cluster: > 1. Infinispan 5.1.5 > 2. java 7u5 64bit > 3. linux 64bit (two nodes debian and one node ubuntu) > 4. tomcat 7.0.28 > 5. jbossTM 4.16.0 JTA only > Tomcat integration code is here: > https://github.com/zvrablik/tomcatInfinispanSessionManager/tree/master/to... > 6. all machines are on real hw ( no virtual machines), date and time is synchronized and shouldn't vary more than 1 second > Reporter: Zdenek Henek > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > Attachments: fgamissueTest2.zip, jgroupsConfig.xml, sessionInfinispanConfigtestLB.xml > > > I am using FineGrainedAtomicMap to store data into clustering distributed cache. When clustering set to replicated doesn't cause any issues or at least I haven't run > into any. When I switch to distributed mode I don't see some key,value pairs in some nodes. This happens randomly. The numOwners is set to two and I have cluster of three nodes. > more details: > https://community.jboss.org/thread/203420?tstart=60 -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3864) numSegments not configurable via Infinispan Server

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-3864: -------------------------------------- Summary: numSegments not configurable via Infinispan Server Key: ISPN-3864 URL: https://issues.jboss.org/browse/ISPN-3864 Project: Infinispan Issue Type: Bug Components: Configuration, Server Affects Versions: 6.0.1.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 6.0.2.Final Hash' numSegments not configurable via Infinispan Server. It still configures virtual nodes. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3862) Upgrade JBoss Marshalling to 1.4.x

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3862?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-3862: ---------------------------------- Assignee: Dan Berindei (was: Galder Zamarreño) > Upgrade JBoss Marshalling to 1.4.x > ----------------------------------- > > Key: ISPN-3862 > URL: https://issues.jboss.org/browse/ISPN-3862 > Project: Infinispan > Issue Type: Feature Request > Components: Marshalling > Reporter: Mircea Markus > Assignee: Dan Berindei > > This is needed not only for moving to the latest and greatest, but alto in order to align with Wildfly 8. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3862) Upgrade JBoss Marshalling to 1.4.x

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3862?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3862: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2312 > Upgrade JBoss Marshalling to 1.4.x > ----------------------------------- > > Key: ISPN-3862 > URL: https://issues.jboss.org/browse/ISPN-3862 > Project: Infinispan > Issue Type: Feature Request > Components: Marshalling > Reporter: Mircea Markus > Assignee: Galder Zamarreño > > This is needed not only for moving to the latest and greatest, but alto in order to align with Wildfly 8. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3704) StateTransfer's PutKeyValueCommand may trigger remote get

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3704?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3704: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1032050|https://bugzilla.redhat.com/show_bug.cgi?id=1032050] from NEW to MODIFIED > StateTransfer's PutKeyValueCommand may trigger remote get > --------------------------------------------------------- > > Key: ISPN-3704 > URL: https://issues.jboss.org/browse/ISPN-3704 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.CR1 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > In TX mode with write skew check on, ST executing puts may trigger a remote get. > The condition in TxDistributionInterceptor.handleTxWriteCommand should probably be switched from > {code} > if (ctx.isOriginLocal() && !skipRemoteGet || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command)) > remoteGetBeforeWrite(ctx, command, recipientGenerator); > {code} > to > {code} > if (!skipRemoteGet && (ctx.isOriginLocal() || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command))) > remoteGetBeforeWrite(ctx, command, recipientGenerator); > {code} > EDIT: > I have also registered a situation where the Prepare/Commit command was executed remotely from within the ST because the topology has changed during the remote get. This should be avoided as well. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3862) Upgrade JBoss Marshalling to 1.4.x

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3862?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3862: ------------------------------- Summary: Upgrade JBoss Marshalling to 1.4.x (was: Upgrade JBossMarshaller to 1.4.x ) > Upgrade JBoss Marshalling to 1.4.x > ----------------------------------- > > Key: ISPN-3862 > URL: https://issues.jboss.org/browse/ISPN-3862 > Project: Infinispan > Issue Type: Feature Request > Components: Marshalling > Reporter: Mircea Markus > Assignee: Galder Zamarreño > > This is needed not only for moving to the latest and greatest, but alto in order to align with Wildfly 8. -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013