July 2009 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-98) Switch test suite to use MPING instead of TCPPING for the tcp stack

by Manik Surtani (JIRA)

Switch test suite to use MPING instead of TCPPING for the tcp stack ------------------------------------------------------------------- Key: ISPN-98 URL: https://jira.jboss.org/jira/browse/ISPN-98 Project: Infinispan Issue Type: Task Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.0.BETA1, 4.0.0.GA This will remove the timeout failures/SuspectExceptions we see on some tests when using JGroups 2.8.x. Will need to alter the multicast address for MPING for each test so that there is no crosstalk. Should test on the Hudson environment as well as local environments. -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-107) make test suite stable

by Mircea Markus (JIRA)

make test suite stable ---------------------- Key: ISPN-107 URL: https://jira.jboss.org/jira/browse/ISPN-107 Project: Infinispan Issue Type: Task Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.BETA1 Make sure that there are no intermittent failures in the suite. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-131) @ConfigurationAttribute to "guess" the attribute name if it is not provided

by Manik Surtani (JIRA)

@ConfigurationAttribute to "guess" the attribute name if it is not provided --------------------------------------------------------------------------- Key: ISPN-131 URL: https://jira.jboss.org/jira/browse/ISPN-131 Project: Infinispan Issue Type: Feature Request Components: Configuration Reporter: Manik Surtani Assignee: Vladimir Blagojevic Fix For: 4.0.0.BETA1 Not sure if it already does this, but doing something like @ConfigurationAttribute(containingElement = "locking") public void setWriteSkewCheck(boolean b) { // ... } The annotation could deduce that the name of the attribute is "writeSkewCheck". -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-106) JdbcXXXCacheStore should honor cacheName

by Klaus Friedel (JIRA)

JdbcXXXCacheStore should honor cacheName ---------------------------------------- Key: ISPN-106 URL: https://jira.jboss.org/jira/browse/ISPN-106 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 4.0.0.ALPHA5 Reporter: Klaus Friedel Assignee: Manik Surtani Creating multiple caches from a CacheManager configured with a JdbcXXXCacheStore results in unpredicted behaviour: After creating a CacheManger that persists its entries with a JdbcXXXCacheStore one will see strange behaviour like this: Cache fooCache = cacheManager.getCache("foo"); Cache barCache = cacheManager.getCache("bar"); // single put: fooCache.put(42, "Hello World"); After restart : fooCache.contains(42); // true barCache.contains(42); // true !!!! To circumvent this behaviour the only solution is to create one CacheStore per Cache. So one migth end up using a lot of different CacheManagers. The best solution IMHO would be to add sopport for a "cacheName" column to "TableManipulation". So different caches could share the same table. -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] Updated: (ISPN-61) Tx optimisations

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-61?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-61: ------------------------------ Fix Version/s: 4.1.0.GA > Tx optimisations > ---------------- > > Key: ISPN-61 > URL: https://jira.jboss.org/jira/browse/ISPN-61 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 4.0.0.ALPHA4 > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.1.0.BETA1, 4.1.0.GA > > > Following 2 optimizations might be implemented with respect to transactions. > 1) From an email on infinispan-dev (horizon-dev actually): > if there are only two members int the cluster always use an 1PC. If the 1st phase fails remotely, then also rollback locally. This would reduce one network roundtrip. > While this is an interesting thought, it does raise the potential for race conditions - since this decision will have to be taken in the TxInterceptor in the beforeCompletion phase of a transaction, and by the time the call gets to the interceptor for replication, the topology may have changed such that you need to replicate to 2 instead of 1 other peer. Which would mean a 2PC again. So it does need some thought. > 2) when asked to prepare, a participant might return a value indicating that no changes were made (read-only participant), so this one won't need an commit message, so less roundtrip. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-102) JOPR plugin should get managed operation and attribute descriptions/display names from annotation

by Manik Surtani (JIRA)

JOPR plugin should get managed operation and attribute descriptions/display names from annotation ------------------------------------------------------------------------------------------------- Key: ISPN-102 URL: https://jira.jboss.org/jira/browse/ISPN-102 Project: Infinispan Issue Type: Feature Request Components: JMX and reporting Affects Versions: 4.0.0.ALPHA4 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.0.BETA1 The JOPR plugin has an RHQ xml file that maps managed attributes to "friendly names". Can this be generated? Each managed attribute/operation is annotated using a @ManagedAttribute/@ManagedOperation annotation, which has a "description". This is the description that should be used in any GUI console. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Updated: (ISPN-61) Tx optimisations

by Mircea Markus (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-61?page=com.atlassian.jira.plugin... ] Mircea Markus updated ISPN-61: ------------------------------ Fix Version/s: 4.1.0.BETA1 (was: 4.0.0.BETA1) (was: 4.0.0.GA) > Tx optimisations > ---------------- > > Key: ISPN-61 > URL: https://jira.jboss.org/jira/browse/ISPN-61 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 4.0.0.ALPHA4 > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.1.0.BETA1 > > > Following 2 optimizations might be implemented with respect to transactions. > 1) From an email on infinispan-dev (horizon-dev actually): > if there are only two members int the cluster always use an 1PC. If the 1st phase fails remotely, then also rollback locally. This would reduce one network roundtrip. > While this is an interesting thought, it does raise the potential for race conditions - since this decision will have to be taken in the TxInterceptor in the beforeCompletion phase of a transaction, and by the time the call gets to the interceptor for replication, the topology may have changed such that you need to replicate to 2 instead of 1 other peer. Which would mean a 2PC again. So it does need some thought. > 2) when asked to prepare, a participant might return a value indicating that no changes were made (read-only participant), so this one won't need an commit message, so less roundtrip. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Work started: (ISPN-31) JPA based cache store

by Alejandro Montenegro (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-31?page=com.atlassian.jira.plugin... ] Work on ISPN-31 started by Alejandro Montenegro. > JPA based cache store > --------------------- > > Key: ISPN-31 > URL: https://jira.jboss.org/jira/browse/ISPN-31 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Manik Surtani > Assignee: Alejandro Montenegro > Fix For: 4.1.0.BETA1, 4.1.0.GA > > > Store that uses JPA for persistence -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-88) reuse code between BinaryCacheStore and StringBasedCacheStore

by Mircea Markus (JIRA)

reuse code between BinaryCacheStore and StringBasedCacheStore ------------------------------------------------------------- Key: ISPN-88 URL: https://jira.jboss.org/jira/browse/ISPN-88 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani There is some code duplication between JdbcStringBasedCacheStore and JdbcBinaryCacheStore, factorize that in a common utility class: Mrthods that need to be considered are: - clear (very similar) - fromStream and toStream (both use PreparedStatements(BLOB, timestamp, key) - loadAll At current time we cannot create a base class for the two stores, as they inherit from different classes. This will need some thought.. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Resolved: (ISPN-56) Create migration script for EHCache

by Mircea Markus (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-56?page=com.atlassian.jira.plugin... ] Mircea Markus resolved ISPN-56. ------------------------------- Resolution: Done done: http://www.jboss.org/community/wiki/ConfigurationMigrationTools > Create migration script for EHCache > ----------------------------------- > > Key: ISPN-56 > URL: https://jira.jboss.org/jira/browse/ISPN-56 > Project: Infinispan > Issue Type: Sub-task > Components: Configuration, Migration tools > Reporter: Manik Surtani > Assignee: Mircea Markus > Fix For: 4.0.0.BETA1, 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2009