October 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1262) Validate that the JCache interceptors are declared in the beans.xml

by Kevin Pollet (JIRA)

Validate that the JCache interceptors are declared in the beans.xml ------------------------------------------------------------------- Key: ISPN-1262 URL: https://issues.jboss.org/browse/ISPN-1262 Project: Infinispan Issue Type: Feature Request Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Priority: Minor We could validate that the JCache interceptors are enabled in the {{beans.xml}} at deployment. This check can be done at {{AfterBeanDiscovery}} phase with {{BeanManager#resolverInterceptors()}} for each JCache annotations. The deployment could fail only when JCache annotations are used in the application. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-1261) Complete the work on the event bridge between Infinispan and CDI

by Kevin Pollet (JIRA)

Complete the work on the event bridge between Infinispan and CDI ---------------------------------------------------------------- Key: ISPN-1261 URL: https://issues.jboss.org/browse/ISPN-1261 Project: Infinispan Issue Type: Task Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet The event bridge (for cache and cache manager) is already implemented in the code but some events are not supported and a deprecated one is used. The following work has to be done on the event bridge: * Remove deprecated event * Support all events * Verify how cache and cache manager observers are registered * Tests * Doc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
12
0 / 0

[JBoss JIRA] (ISPN-2143) Improve how different indexed caches sync up on new indexed types

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2143: ------------------------------------- Summary: Improve how different indexed caches sync up on new indexed types Key: ISPN-2143 URL: https://issues.jboss.org/browse/ISPN-2143 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.2.0.FINAL Currently when a node receives an unknown type, it doesn't inform all other nodes, which might fail to get metadata and index boot information from it. Also, the list of known types should be stored somewhere. When a shared index is used, we might be able to load some type names from the index itself, but unfortunately usually we need the type name to initialize the index. Rely on an index storage convention? See also comments in {{org.infinispan.query.indexmanager.IndexUpdateCommand}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] (ISPN-1893) Query module demo

by Mathieu Lachance (JIRA)

Mathieu Lachance created ISPN-1893: -------------------------------------- Summary: Query module demo Key: ISPN-1893 URL: https://issues.jboss.org/browse/ISPN-1893 Project: Infinispan Issue Type: Task Components: Core API, Locking and Concurrency, Migration tools Reporter: Mathieu Lachance Assignee: Manik Surtani Would it be possible to make a query-module demo showing the best practice with : - replication clustering mode + local query, - distribution clustering mode + index replication + local query, - distribution clustering mode + clustered query I guess this would be easy to integrate it in the already existant gui demo. Big thanks ! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
7
0 / 0

[JBoss JIRA] (ISPN-2366) Allow getCache() to return before the node receives any state

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2366: ---------------------------------- Summary: Allow getCache() to return before the node receives any state Key: ISPN-2366 URL: https://issues.jboss.org/browse/ISPN-2366 Project: Infinispan Issue Type: Task Components: State transfer Affects Versions: 5.2.0.Alpha4 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.Final With NBST it's possible to use a cache without having any local state. We should allow getCache() to return as soon as the joiner has received a consistent hash (actually CacheTopology) from the coordinator. This is related to ISPN-1394 - joiners should be able to work even if rebalancing is blocked. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] (ISPN-1925) Upgrade to JCache 0.5

by Kevin Pollet (JIRA)

Kevin Pollet created ISPN-1925: ---------------------------------- Summary: Upgrade to JCache 0.5 Key: ISPN-1925 URL: https://issues.jboss.org/browse/ISPN-1925 Project: Infinispan Issue Type: Component Upgrade Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.2.0.ALPHA1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
8
0 / 0

[JBoss JIRA] (ISPN-2278) Implicit transaction enabling during configuration fails

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2278: ---------------------------------- Summary: Implicit transaction enabling during configuration fails Key: ISPN-2278 URL: https://issues.jboss.org/browse/ISPN-2278 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.6.FINAL Reporter: Thomas Fromm Assignee: Mircea Markus The implicit enabling of transaction support does not work in all cases described in TransactionMode Javadoc inside the current configuration API. - transactionManagerLookup is explicit configured This works not in programmatic. - enabled batching When using XML configuration, this will not work, when only <invocationBatching> element and no <transaction> element is used. At ConfigurationBuilderHolder.newConfigurationBuilder(...) the default cache config is used as base for the new named cache. Since build() is called, the TransactionConfiguration is set to NON_TRANSACTIONAL in the Configuration template used for the new ConfigurationBuilder. Later then any if(transactionMode == null)-related conditions in TransactionConfigurationBuilder will fail. ISPN-2276 _maybe_ also points to this problem, did not spent further investigation on it. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] (ISPN-2141) Better configuration options for Infinispan Query

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2141: ------------------------------------- Summary: Better configuration options for Infinispan Query Key: ISPN-2141 URL: https://issues.jboss.org/browse/ISPN-2141 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.2.0.ALPHA2 Rethink the configuration options for Query. See also https://community.jboss.org/wiki/InfinispanQuery-DesignAndPlanning -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
9
0 / 0

[JBoss JIRA] (ISPN-2082) JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes

by Ryan Scharer (JIRA)

Ryan Scharer created ISPN-2082: ---------------------------------- Summary: JdbcStringBasedCacheStore: ORA-24816 when storing BLOB values > 4000 bytes Key: ISPN-2082 URL: https://issues.jboss.org/browse/ISPN-2082 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.1.5.FINAL Environment: OS X 10.7.4, JDK 1.7.0u4 Reporter: Ryan Scharer Assignee: Manik Surtani I've configured a JdbcStringBasedCacheStore with a VARCHAR(4000) key column and a BLOB value column. If I try to store a BLOB value of less than 4000 bytes, everything works fine. If the value is greater, the cache store fails with ORA-24816. This occurs because the BLOB column is not the last one in the PreparedStatement SQL as the Oracle driver requires. My current, sad workaround is to clone the JdbcStringBasedCacheStore implementation and write my own insert/update SQL in storeLockSafe(). This works fine, but obviously isn't ideal from an upgrade point of view. Simply overriding storeLockSafe() isn't an option due to all the private fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
23
0 / 0

[JBoss JIRA] (ISPN-2354) AsyncStoreFunctionalTest fails intermittently

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2354?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2354: -------------------------------- Fix Version/s: 6.0.0.Final (was: 5.2.0.CR1) > AsyncStoreFunctionalTest fails intermittently > --------------------------------------------- > > Key: ISPN-2354 > URL: https://issues.jboss.org/browse/ISPN-2354 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.0.Alpha4 > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 6.0.0.Final > > > AsyncStoreFunctionalTest sometimes fails with this assertion error: > {noformat} > 14:49:46,380 ERROR (testng-AsyncStoreFunctionalTest:) [UnitTestTestNGListener] Test testGetAfterRemove(org.infinispan.loaders.decorators.AsyncStoreFunctionalTest) failed. > java.lang.AssertionError: Keys not empty: [1] > at org.testng.AssertJUnit.fail(AssertJUnit.java:57) > at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:22) > at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest$3.call(AsyncStoreFunctionalTest.java:211) > at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1252) > at org.infinispan.loaders.decorators.AsyncStoreFunctionalTest.testGetAfterRemove(AsyncStoreFunctionalTest.java:165) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:673) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1147) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {noformat} -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2012