June 2009 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Resolved: (ISPN-54) Create migration script for JBoss Cache 3.1

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-54?page=com.atlassian.jira.plugin... ] Manik Surtani resolved ISPN-54. ------------------------------- Fix Version/s: 4.0.0.ALPHA4 (was: 4.0.0.BETA1) Resolution: Done > Create migration script for JBoss Cache 3.1 > ------------------------------------------- > > Key: ISPN-54 > URL: https://jira.jboss.org/jira/browse/ISPN-54 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration, Migration tools > Reporter: Manik Surtani > Assignee: Mircea Markus > Fix For: 4.0.0.ALPHA4, 4.0.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (ISPN-70) Transparent eager locking for transactions

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-70?page=com.atlassian.jira.plugin... ] Manik Surtani resolved ISPN-70. ------------------------------- Resolution: Done > Transparent eager locking for transactions > ------------------------------------------ > > Key: ISPN-70 > URL: https://jira.jboss.org/jira/browse/ISPN-70 > Project: Infinispan > Issue Type: Feature Request > Components: Locking and Concurrency, Transactions > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 4.0.0.ALPHA4, 4.0.0.GA > > > Allow a configuration attribute on <transaction /> to be able to specify whether cluster-wide locks are acquired eagerly or lazily. The current scheme (lazy) should be the default. > This could be implemented by broadcasting LockControlCommands alongside acquiring local locks for necessary keys. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-70) Transparent eager locking for transactions

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-70?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-70: ------------------------------ Fix Version/s: 4.0.0.ALPHA4 (was: 4.0.0.BETA1) > Transparent eager locking for transactions > ------------------------------------------ > > Key: ISPN-70 > URL: https://jira.jboss.org/jira/browse/ISPN-70 > Project: Infinispan > Issue Type: Feature Request > Components: Locking and Concurrency, Transactions > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 4.0.0.ALPHA4, 4.0.0.GA > > > Allow a configuration attribute on <transaction /> to be able to specify whether cluster-wide locks are acquired eagerly or lazily. The current scheme (lazy) should be the default. > This could be implemented by broadcasting LockControlCommands alongside acquiring local locks for necessary keys. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Reopened: (ISPN-54) Create migration script for JBoss Cache 3.1

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-54?page=com.atlassian.jira.plugin... ] Manik Surtani reopened ISPN-54: ------------------------------- > Create migration script for JBoss Cache 3.1 > ------------------------------------------- > > Key: ISPN-54 > URL: https://jira.jboss.org/jira/browse/ISPN-54 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration, Migration tools > Reporter: Manik Surtani > Assignee: Mircea Markus > Fix For: 4.0.0.ALPHA4, 4.0.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-82) Expose the cache version in the CacheManager MBean

by Heiko W. Rupp (JIRA)

Expose the cache version in the CacheManager MBean -------------------------------------------------- Key: ISPN-82 URL: https://jira.jboss.org/jira/browse/ISPN-82 Project: Infinispan Issue Type: Sub-task Components: JMX and reporting Affects Versions: 4.0.0.ALPHA3 Reporter: Heiko W. Rupp Assignee: Manik Surtani The cache manager mbean should expose the version string (e.g. 'Starobrno' 4.0.0.ALPHA3 ) in a 'version' attribute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
5
0 / 0

[JBoss JIRA] Reopened: (ISPN-70) Transparent eager locking for transactions

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-70?page=com.atlassian.jira.plugin... ] Manik Surtani reopened ISPN-70: ------------------------------- > Transparent eager locking for transactions > ------------------------------------------ > > Key: ISPN-70 > URL: https://jira.jboss.org/jira/browse/ISPN-70 > Project: Infinispan > Issue Type: Feature Request > Components: Locking and Concurrency, Transactions > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 4.0.0.BETA1, 4.0.0.GA > > > Allow a configuration attribute on <transaction /> to be able to specify whether cluster-wide locks are acquired eagerly or lazily. The current scheme (lazy) should be the default. > This could be implemented by broadcasting LockControlCommands alongside acquiring local locks for necessary keys. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-20) check whether locking is needed within JDBC cache stores

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-20?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-20: ------------------------------ Fix Version/s: 4.1.0.BETA1 4.1.0.GA (was: 4.0.0.BETA1) (was: 4.0.0.GA) > check whether locking is needed within JDBC cache stores > -------------------------------------------------------- > > Key: ISPN-20 > URL: https://jira.jboss.org/jira/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.1.0.BETA1, 4.1.0.GA > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-20?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-20: ------------------------------ Summary: check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE (was: check whether locking is needed within JDBC cache stores) > check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE > --------------------------------------------------------------------------------- > > Key: ISPN-20 > URL: https://jira.jboss.org/jira/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.1.0.BETA1, 4.1.0.GA > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Reopened: (ISPN-20) check whether locking is needed within JDBC cache stores

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-20?page=com.atlassian.jira.plugin... ] Manik Surtani reopened ISPN-20: ------------------------------- > check whether locking is needed within JDBC cache stores > -------------------------------------------------------- > > Key: ISPN-20 > URL: https://jira.jboss.org/jira/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.1.0.BETA1, 4.1.0.GA > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-20) check whether locking is needed within JDBC cache stores

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-20?page=com.atlassian.jira.plugin... ] Manik Surtani commented on ISPN-20: ----------------------------------- What about using a SELECT FOR UPDATE semantic in when reading the entry? > check whether locking is needed within JDBC cache stores > -------------------------------------------------------- > > Key: ISPN-20 > URL: https://jira.jboss.org/jira/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.0.0.BETA1, 4.0.0.GA > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2009