August 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-800) Infinispan inside OSGI

by luca stancapiano (JIRA)

Infinispan inside OSGI ---------------------- Key: ISPN-800 URL: https://jira.jboss.org/browse/ISPN-800 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 4.2.0.CR1 Reporter: luca stancapiano Assignee: Manik Surtani We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixed in jgroups 1.12) river 1.2.3.GA marshalling-api 1.2.3.GA jboss common core 2.2.14.GA jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

6
61
0 / 0

[JBoss JIRA] Created: (ISPN-1195) Rehashing and state transfer to use digesting

by Manik Surtani (JIRA)

Rehashing and state transfer to use digesting --------------------------------------------- Key: ISPN-1195 URL: https://issues.jboss.org/browse/ISPN-1195 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache, State transfer Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Dan Berindei Priority: Critical Fix For: 5.1.0.BETA1, 5.1.0.Final Rather than pushing entire state to new joiners, a mechanism of digests should be used to minimise network transfers. For example, Merkle trees can be used to determine which entries are out of date and need pushing, in the case of nodes that persist to a local cache store, and is restarted but still has access to some state on disk. This would require versioned entries though. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (ISPN-2202) Setup code coverage reporting in Infinispan

by Martin Gencur (JIRA)

Martin Gencur created ISPN-2202: ----------------------------------- Summary: Setup code coverage reporting in Infinispan Key: ISPN-2202 URL: https://issues.jboss.org/browse/ISPN-2202 Project: Infinispan Issue Type: Feature Request Reporter: Martin Gencur Assignee: Anna Manukyan Set up code coverage reporting in community Infinispan (master branch). * Use JaCoCo tool * Create a separate Maven profile for enabling the reporting (e.g. -Pcoverage) - try to minimize code changes in pom files -> e.g. configure this in parent and then just inherit in submodules * Create a Jenkins job under EDG-QE tab * Try to identify weakly covered non-trivial code (don't care about trivial code like setters, getters, simple utility methods etc.) -- 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

11 years, 8 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2191) Defaultcachemanager.getCache(name) is slow

by Dominik Obermaier (JIRA)

Dominik Obermaier created ISPN-2191: --------------------------------------- Summary: Defaultcachemanager.getCache(name) is slow Key: ISPN-2191 URL: https://issues.jboss.org/browse/ISPN-2191 Project: Infinispan Issue Type: Enhancement Affects Versions: 5.1.5.FINAL Reporter: Dominik Obermaier Assignee: Manik Surtani Priority: Minor With the help of JVisualVM I found out, that 63% cpu time of the application was needed in org.infinispan.loaders.file.FileCacheStore.lodaBucket and 25% in org.infinispan.DefaultCacheManager$Cachewrapper.getCache. The workaround is to share one instance of the cache for all classes, so a getCache("name) can be avoided. -- 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

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2201) Make a distinction between user-level and internal flags

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2201: -------------------------------------- Summary: Make a distinction between user-level and internal flags Key: ISPN-2201 URL: https://issues.jboss.org/browse/ISPN-2201 Project: Infinispan Issue Type: Enhancement Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 6.0.0.FINAL This confusion is highlighted by ISPN-2187. User-level flags, i.e. FORCE_WRITE_LOCK, should be separated from those that are purely internal, i.e. PUT_FOR_EXTERNAL_READ. Obviously, user-level flags might be used for internal purpouses, but by making the separation and putting the internal-only flags separately, we should avoid misuse. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2180) startServer.bat doesn't doesn't reference the log4j.xml correctly

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2180: ----------------------------------- Summary: startServer.bat doesn't doesn't reference the log4j.xml correctly Key: ISPN-2180 URL: https://issues.jboss.org/browse/ISPN-2180 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.5.FINAL Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.FINAL the log4j file is reference with absolute path. This works if one runs the script from the bin directory but doesn't work if the caller invokes startServer.bat from the parent. -- 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

11 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1379) cache startup error with named cache element <evictions maxEntries="-1"/> overriding defaults

by Jan Slezak (JIRA)

cache startup error with named cache element <evictions maxEntries="-1"/> overriding defaults --------------------------------------------------------------------------------------------- Key: ISPN-1379 URL: https://issues.jboss.org/browse/ISPN-1379 Project: Infinispan Issue Type: Bug Reporter: Jan Slezak Assignee: Manik Surtani if there is defined for example <eviction maxEntries="10" strategy="FIFO"/> in <default/> and there is redefinition <eviction maxEntries="-1"/> in named cache - the cache reports error during startup: org.infinispan.config.ConfigurationException: Eviction maxEntries value cannot be less than or equal to zero if eviction is enabled -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
5
0 / 0

[JBoss JIRA] (ISPN-2147) Subclasses of AbstractClusteredWriteSkewTest can hang because of ISPN-2081

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2147: ---------------------------------- Summary: Subclasses of AbstractClusteredWriteSkewTest can hang because of ISPN-2081 Key: ISPN-2147 URL: https://issues.jboss.org/browse/ISPN-2147 Project: Infinispan Issue Type: Bug Components: Test Suite Affects Versions: 5.2.0.ALPHA1 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Critical Fix For: 5.2.0.ALPHA2 -- 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

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] (ISPN-2182) Some DefaultCacheManager constructors still performing legacy configuration adaptation

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-2182: ---------------------------------- Summary: Some DefaultCacheManager constructors still performing legacy configuration adaptation Key: ISPN-2182 URL: https://issues.jboss.org/browse/ISPN-2182 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.2.0.ALPHA2 Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Minor Fix For: 5.2.0.ALPHA3 e.g. public DefaultCacheManager(GlobalConfiguration globalConfiguration, boolean start) public DefaultCacheManager(GlobalConfiguration globalConfiguration) This causes some properties to get lost, e.g. classloader -- 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

11 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (ISPN-375) Enable Hot Rod clients to start transactions

by Galder Zamarreno (JIRA)

Enable Hot Rod clients to start transactions -------------------------------------------- Key: ISPN-375 URL: https://jira.jboss.org/jira/browse/ISPN-375 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.1.0.BETA1, 5.1.0.Final It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only. This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction. Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky. -- 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

11 years, 8 months

6
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2012