December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3861) Add a document entry describing how to read/write data between the Cpp and Java clients

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3861: ----------------------------------- Summary: Add a document entry describing how to read/write data between the Cpp and Java clients Key: ISPN-3861 URL: https://issues.jboss.org/browse/ISPN-3861 Project: Infinispan Issue Type: Feature Request Components: Documentation Affects Versions: 6.0.1.Final Reporter: Mircea Markus Assignee: Mircea Markus This should be a new chapter, at the same level with the java hotrod client chapter[1], and it should contain links to the quick start. Also search and remove: "TODO Add reference to sample in C++ client user guide" from the used doc. [1] http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_java_hot_rod... -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3860) The ISPN 6.0 documentation mentions startServer.sh as a way to start an Infinispan server

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3860: ----------------------------------- Summary: The ISPN 6.0 documentation mentions startServer.sh as a way to start an Infinispan server Key: ISPN-3860 URL: https://issues.jboss.org/browse/ISPN-3860 Project: Infinispan Issue Type: Feature Request Components: Documentation Affects Versions: 6.0.0.Final Reporter: Mircea Markus Assignee: Galder Zamarreño http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_using_hot_ro... Starting with 5.3 we use the AS for starting a server. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3847) Improve resilience of ModuleLifecycle loading

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/ISPN-3847?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated ISPN-3847: ------------------------------- Affects Version/s: 6.0.1.Final (was: 6.0.0.Final) > Improve resilience of ModuleLifecycle loading > --------------------------------------------- > > Key: ISPN-3847 > URL: https://issues.jboss.org/browse/ISPN-3847 > Project: Infinispan > Issue Type: Enhancement > Components: Core API > Affects Versions: 6.0.1.Final > Reporter: Paul Ferraro > Assignee: Mircea Markus > > Currently, org.infinispan.util.ModuleProperties.resolveModuleLifecycles(...) uses a ServiceLoader to directly load ModuleLifecycle instances. However, if a jar exists on the classpath containing a META-INF/services/org.infinispan.lifecycle.ModuleLifecycle file, but the class name contained within cannot be loaded, due to, for example, a dependency jar being missing, then the whole resolveModuleLifecycles(...) method chokes due to a ServiceConfigurationError. For example, if infinispan-query is on the classpath, but hibernate-search is not, Infinispan is unusable. > I can see 2 ways to fix this: > 1. Use the iterator directly instead of the enhanced for-loop, and catch and handle the SCE: > e.g. > {code:java} > Iterator<ModuleLifecycle> lifecycles = ServiceLoader.load(ModuleLifecycle.class, classLoader); > while (lifecycles.hasNext()) { > try { > ModuleLifecycle lifecycle = lifecycles.next(); // This can throw SCE > result.add(lifecycle); > } catch (ServiceConfigurationError e) { > // Log error > } > } > {code} > 2. Introduce a ModuleLifecycleProvider abstraction - that won't throw an SCE. The ServiceLoader spec actually recommends this: > "The provider class is typically not the entire provider itself but rather a proxy which contains enough information to decide whether the provider is able to satisfy a particular request together with code that can create the actual provider on demand." > In the end, this would look something like: > {code:java} > for (ModuleLifecycleFactory factory: ServiceLoader.load(ModuleLifecycleFactory.class, classLoader)) { > if (factory.isEnabled()) { // returns true if create method will not throw SCE > ModuleLifecycle lifecycle = factory.createModuleLifecycle(); > result.add(lifecycle); > } > } > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3834) New advanced indexing flag to skip deletion of previous entry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3834?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3834: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1045082|https://bugzilla.redhat.com/show_bug.cgi?id=1045082] from NEW to CLOSED > New advanced indexing flag to skip deletion of previous entry > ------------------------------------------------------------- > > Key: ISPN-3834 > URL: https://issues.jboss.org/browse/ISPN-3834 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > I'm needing to add a org.infinispan.context.Flag.SKIP_INDEX_CLEANUP which does not issue an UPDATE index command but a simple ADD. > Just ADD is way more efficient, just we can't automatically detect it safely so I need a flag to allow for efficient data import. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3586) Improve performance of Infinispan Lucene directory provider

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3586?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3586: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1045082|https://bugzilla.redhat.com/show_bug.cgi?id=1045082] from NEW to CLOSED > Improve performance of Infinispan Lucene directory provider > ----------------------------------------------------------- > > Key: ISPN-3586 > URL: https://issues.jboss.org/browse/ISPN-3586 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Affects Versions: 6.0.0.Beta2 > Reporter: Adrian Nistor > Assignee: Sanne Grinovero > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > Currently in distributed mode it takes about 2 minutes to index 2000 entries. This was found in ISPN-3102. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3833) QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3833?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3833: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1045082|https://bugzilla.redhat.com/show_bug.cgi?id=1045082] from NEW to CLOSED > QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently > ------------------------------------------------------------------------------------------ > > Key: ISPN-3833 > URL: https://issues.jboss.org/browse/ISPN-3833 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > The QueryInterceptor should use a local cache to avoid unnecessary invocations, especially as the cluster registry is transactional this is a source of garbage generation. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3844) Cluster Registry cache does not need to provide return value for put and remove

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3844?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3844: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1045082|https://bugzilla.redhat.com/show_bug.cgi?id=1045082] from NEW to CLOSED > Cluster Registry cache does not need to provide return value for put and remove > ------------------------------------------------------------------------------- > > Key: ISPN-3844 > URL: https://issues.jboss.org/browse/ISPN-3844 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > This internal registry needs to be efficient, and the return types of put and remove operations are redundant for our purposes: I'm removing them. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3859) Leveldb tests fail on RHEL6 64bit randomly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3859?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3859: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1045109 > Leveldb tests fail on RHEL6 64bit randomly > ------------------------------------------ > > Key: ISPN-3859 > URL: https://issues.jboss.org/browse/ISPN-3859 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Reporter: Jakub Markos > Assignee: Mircea Markus > Attachments: console_log.txt, server.log > > > This test https://github.com/infinispan/infinispan/blob/master/server/integration/t... fails randomly on RHEL6 64bit (both oracle/ibm java 7) with latest infinispan server SNAPSHOT. > testDataSurvivesRestart(org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreTest): expected:<1> but was:<null> (line 90) > testDataRetrievableViaLevelDbApi(org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreTest): expected:<1> but was:<null> (line 125) > I didn't reproduce it locally so far so I couldn't investigate much. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3859) Leveldb tests fail on RHEL6 64bit randomly

by Jakub Markos (JIRA)

[ https://issues.jboss.org/browse/ISPN-3859?page=com.atlassian.jira.plugin.... ] Jakub Markos updated ISPN-3859: ------------------------------- Attachment: console_log.txt server.log > Leveldb tests fail on RHEL6 64bit randomly > ------------------------------------------ > > Key: ISPN-3859 > URL: https://issues.jboss.org/browse/ISPN-3859 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Reporter: Jakub Markos > Assignee: Mircea Markus > Attachments: console_log.txt, server.log > > > This test https://github.com/infinispan/infinispan/blob/master/server/integration/t... fails randomly on RHEL6 64bit (both oracle/ibm java 7) with latest infinispan server SNAPSHOT. > testDataSurvivesRestart(org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreTest): expected:<1> but was:<null> (line 90) > testDataRetrievableViaLevelDbApi(org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreTest): expected:<1> but was:<null> (line 125) > I didn't reproduce it locally so far so I couldn't investigate much. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3859) Leveldb tests fail on RHEL6 64bit randomly

by Jakub Markos (JIRA)

[ https://issues.jboss.org/browse/ISPN-3859?page=com.atlassian.jira.plugin.... ] Jakub Markos commented on ISPN-3859: ------------------------------------ You can run the test using 'mvn clean verify -Psuite.cachestore -Dtest=LevelDBCacheStoreTest -Dleveldb.patch -Dlog.level.infinispan=TRACE' in infinispan/server/integration/testsuite. Attached console and server logs. > Leveldb tests fail on RHEL6 64bit randomly > ------------------------------------------ > > Key: ISPN-3859 > URL: https://issues.jboss.org/browse/ISPN-3859 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Reporter: Jakub Markos > Assignee: Mircea Markus > > This test https://github.com/infinispan/infinispan/blob/master/server/integration/t... fails randomly on RHEL6 64bit (both oracle/ibm java 7) with latest infinispan server SNAPSHOT. > testDataSurvivesRestart(org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreTest): expected:<1> but was:<null> (line 90) > testDataRetrievableViaLevelDbApi(org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreTest): expected:<1> but was:<null> (line 125) > I didn't reproduce it locally so far so I couldn't investigate much. -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013