July 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1274) DefaultExecutorService uses no thread pool when it decides to invokeLocally

by Thomas Peuss (JIRA)

DefaultExecutorService uses no thread pool when it decides to invokeLocally --------------------------------------------------------------------------- Key: ISPN-1274 URL: https://issues.jboss.org/browse/ISPN-1274 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.0.0.CR8 Reporter: Thomas Peuss Assignee: Manik Surtani DefaultExecutorService uses no thread pool when it decides to invokeLocally. It always uses the calling thread in this case. This leads to bad concurrency (1). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

7
9
0 / 0

[JBoss JIRA] Created: (ISPN-1129) method o.i.distexec.DefaultExecutorService.invokeAny(Collection tasks) never returns

by Mikhail Khludnev (JIRA)

method o.i.distexec.DefaultExecutorService.invokeAny(Collection tasks) never returns ------------------------------------------------------------------------------------ Key: ISPN-1129 URL: https://issues.jboss.org/browse/ISPN-1129 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.0.0.CR3 Reporter: Mikhail Khludnev Assignee: Manik Surtani DefaultExecutorService.invokeAny() seems not working ever just because DistributedExecutionCompletionService seems not working too, because it never attach it's listener to tasks. I made a test, but didn't find an easy approach to fix it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (ISPN-387) Enable accessing Hot Rod servers via WebSockets

by Galder Zamarreno (JIRA)

Enable accessing Hot Rod servers via WebSockets ----------------------------------------------- Key: ISPN-387 URL: https://jira.jboss.org/jira/browse/ISPN-387 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 Add a flag to Hot Rod server configuration so that appropiate Base64 encoder/decoder can be used when interfacing with WebSocket clients. This might also require for Netty WebSocket channel handlers to be set up so that WebSocket upgrade handshaking can be dealt with independent of Hot Rod. -- 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

12 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-78) Large object support

by Manik Surtani (JIRA)

Large object support -------------------- Key: ISPN-78 URL: https://jira.jboss.org/jira/browse/ISPN-78 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.GA if each VM is allocated a 2GB heap and you have a 100 nodes in a grid with 1 redundant copy for each key, you have a theoretical addressable heap of 100GB. But you are limited by (half) the heap of a single VM per entry, since entries are stored whole. E.g., cache.put(k, my2GBObject) will fail since you need at least 2GB for the object + another 2GB for its serialized form. This gets worse when you try cache.put(k, my10GBObject). This *should* be possible if we have a theoretical 100GB heap. Potential solutions here are to fragment large objects, and store each fragment under separate keys. Another approach would be to directly stream objects to disk. etc. Needs thought and design, possibly a separate API to prevent 'pollution" of the more simplistic API. (JumboCache?) Re: fragmenting, issues to overcome: How many chunks to fragment into? Max size of each key could be configured, but how do we determine the size of an Object? VM instrumentation? Or perhaps the JumboCache only stores byte[]'s? -- 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

12 years, 3 months

10
32
0 / 0

[JBoss JIRA] Created: (ISPN-686) JdbcStringBasedCacheStore loads previous data from store before an insert

by Sanne Grinovero (JIRA)

JdbcStringBasedCacheStore loads previous data from store before an insert ------------------------------------------------------------------------- Key: ISPN-686 URL: https://jira.jboss.org/browse/ISPN-686 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final, 4.0.0.Final Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.2.0.Final, 5.0.0.Final The JdbcStringBasedCacheStore implementation loads the previous data on an insert to find out if it should generate an UPDATE or INSERT statement, while it would perform much better to just verify if the primary key exists. On top of this, some databases provide ways to avoid the need to check at all, like MySQL's " INSERT ... ON DUPLICATE KEY UPDATE" [http://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

7
29
0 / 0

[JBoss JIRA] Created: (ISPN-750) Infinispan servers should be accessible via SSL sockets

by Galder Zamarreño (JIRA)

Infinispan servers should be accessible via SSL sockets ------------------------------------------------------- Key: ISPN-750 URL: https://jira.jboss.org/browse/ISPN-750 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA1, 5.1.0.Final Clients should be able to configure Hot Rod/Memcached servers for SSL access, in order to encrypt communications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[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

12 years, 4 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

12 years, 4 months

2
6
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

12 years, 4 months

6
12
0 / 0

[JBoss JIRA] Created: (ISPN-1235) Per class(es) logging settings in testsuite

by Galder Zamarreño (JIRA)

Per class(es) logging settings in testsuite ------------------------------------------- Key: ISPN-1235 URL: https://issues.jboss.org/browse/ISPN-1235 Project: Infinispan Issue Type: Enhancement Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.Final Just brainstorming: It'd be very useful to have a way to run the testsuite with normal logging settings but have the ability to define one or more test classes as having TRACE on x.y.z. This could be useful for those elusive failures that only happen when the testsuite runs! Clearly, it'd need some programmatic magic to enable/disable the logging at runtime, but there's some benefit to all this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2011