February 2013 - infinispan-issues

[JBoss JIRA] (ISPN-2824) Excluive lock operation required to support invokeEntryProcessor()

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2824?page=com.atlassian.jira.plugin.... ] Work on ISPN-2824 started by Galder Zamarreño. > Excluive lock operation required to support invokeEntryProcessor() > ------------------------------------------------------------------ > > Key: ISPN-2824 > URL: https://issues.jboss.org/browse/ISPN-2824 > Project: Infinispan > Issue Type: Sub-task > Components: Locking and Concurrency > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > Exclusive lock semantics are needed within Infinispan in order to support JSR-107's invokeEntryProcessor() method. See dev thread for detailed information. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2832) upgrade to JGroups 3.3.0.Alpha2

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2832?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2832: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1670 > upgrade to JGroups 3.3.0.Alpha2 > ------------------------------- > > Key: ISPN-2832 > URL: https://issues.jboss.org/browse/ISPN-2832 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > this is a requirement for TO integration. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2832) upgrade to JGroups 3.3.0.Alpha2

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2832?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2832: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > upgrade to JGroups 3.3.0.Alpha2 > ------------------------------- > > Key: ISPN-2832 > URL: https://issues.jboss.org/browse/ISPN-2832 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > this is a requirement for TO integration. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2766) Improve and adapt notification model to fit JSR107 notification model

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2766?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2766: ---------------------------------------- To summarise some of the issues highlighted in the mailing list: * When an entry is created, no cache entry updated/modified events must be fired. Since JSR-107 notifications only support one callback, this should be done after the event, but with CacheEntryModified event, you only know if the event was for an entry created or not when isPre=false. Adding an isCreated() to CacheEntryModifiedEvent should just work. > Improve and adapt notification model to fit JSR107 notification model > --------------------------------------------------------------------- > > Key: ISPN-2766 > URL: https://issues.jboss.org/browse/ISPN-2766 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Affects Versions: 5.2.0.CR3 > Reporter: Vladimir Blagojevic > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > Out current notification (listener) model does not fit JSR 107 notification model and thus needs a slight adaptation in order to implement JSR 107. > More specifically the problem is with JSR107 CacheEntryCreatedListener and CacheEntryExpiredListener. > The first one is not easy to implement because we need both key/value pair for jsr listener and our CacheEntryCreatedEvent does not provide value. > The second is related to CacheEntryExpired event. True, spec is not rigorous that such an event has to be fired immediately after an entry has expired but eventually (which might be on access). However, we do not have such an event at all as of now. > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2766) Improve and adapt notification model to fit JSR107 notification model

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2766?page=com.atlassian.jira.plugin.... ] Work on ISPN-2766 started by Galder Zamarreño. > Improve and adapt notification model to fit JSR107 notification model > --------------------------------------------------------------------- > > Key: ISPN-2766 > URL: https://issues.jboss.org/browse/ISPN-2766 > Project: Infinispan > Issue Type: Sub-task > Components: Listeners > Affects Versions: 5.2.0.CR3 > Reporter: Vladimir Blagojevic > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > Out current notification (listener) model does not fit JSR 107 notification model and thus needs a slight adaptation in order to implement JSR 107. > More specifically the problem is with JSR107 CacheEntryCreatedListener and CacheEntryExpiredListener. > The first one is not easy to implement because we need both key/value pair for jsr listener and our CacheEntryCreatedEvent does not provide value. > The second is related to CacheEntryExpired event. True, spec is not rigorous that such an event has to be fired immediately after an entry has expired but eventually (which might be on access). However, we do not have such an event at all as of now. > -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2639) Write an adaptor for the JSR 107 API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2639?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2639: ---------------------------------------- ISPN-2767 completed with: https://github.com/galderz/infinispan/commit/5d6e50620ef2ec0368273a2c6c30... With this, we're currently at: {code}Tests run: 286, Failures: 22, Errors: 1, Skipped: 0{cogde} https://gist.github.com/galderz/d4efa20c087db5f136da > Write an adaptor for the JSR 107 API > ------------------------------------ > > Key: ISPN-2639 > URL: https://issues.jboss.org/browse/ISPN-2639 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > This should be a new Infinispan maven module, implement the API and pass the TCK suite as defined here: https://github.com/jsr107 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2639) Write an adaptor for the JSR 107 API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2639?page=com.atlassian.jira.plugin.... ] Galder Zamarreño edited comment on ISPN-2639 at 2/19/13 8:56 AM: ----------------------------------------------------------------- ISPN-2767 completed with: https://github.com/galderz/infinispan/commit/5d6e50620ef2ec0368273a2c6c30... With this, we're currently at: {code}Tests run: 286, Failures: 22, Errors: 1, Skipped: 0{code} https://gist.github.com/galderz/d4efa20c087db5f136da was (Author: galder.zamarreno): ISPN-2767 completed with: https://github.com/galderz/infinispan/commit/5d6e50620ef2ec0368273a2c6c30... With this, we're currently at: {code}Tests run: 286, Failures: 22, Errors: 1, Skipped: 0{cogde} https://gist.github.com/galderz/d4efa20c087db5f136da > Write an adaptor for the JSR 107 API > ------------------------------------ > > Key: ISPN-2639 > URL: https://issues.jboss.org/browse/ISPN-2639 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > This should be a new Infinispan maven module, implement the API and pass the TCK suite as defined here: https://github.com/jsr107 -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2833) Add new tests for testing Lucene v3 & v4 as well increasing code coverage.

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2833?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2833: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1656 > Add new tests for testing Lucene v3 & v4 as well increasing code coverage. > -------------------------------------------------------------------------- > > Key: ISPN-2833 > URL: https://issues.jboss.org/browse/ISPN-2833 > Project: Infinispan > Issue Type: Task > Components: Lucene Directory > Reporter: Anna Manukyan > Assignee: Anna Manukyan > > New tests should be added for verifying the Lucene Directory & increasing it's coverage. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2834) test failure: AtomicMapBackupTest

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2834: ----------------------------------- Summary: test failure: AtomicMapBackupTest Key: ISPN-2834 URL: https://issues.jboss.org/browse/ISPN-2834 Project: Infinispan Issue Type: Bug Components: Cross-Site Replication Affects Versions: 5.2.2.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2584) BackupReceiver survives cache shutdown

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2584?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2584: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1672 > BackupReceiver survives cache shutdown > -------------------------------------- > > Key: ISPN-2584 > URL: https://issues.jboss.org/browse/ISPN-2584 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 5.2.0.Beta5 > Reporter: Radim Vansa > Assignee: Mircea Markus > Fix For: 5.2.2.Final, 5.3.0.Final > > > When the cache manager is stopped together with all caches, the static field {{BackupReceiverRepositoryImpl.backupReceivers}} is not cleaned up. When another cache manager is started and we try to XS replicate into this node, the request reaches {{BackupReceiver}} with references to the old, stopped cache. This instance has TERMINATED ComponentRepository without {{TransactionTable}} and this results in {{NullPointerException}} in {{BackupCacheUpdater.replayModificationsInTransaction}}. > When the cache is stopped, it should remove all references to it from the {{BackupReceiverRepositoryImpl.backupReceivers}}. -- 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

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2013