April 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-951) Infinispan Query module should load entities using getAsync

by Sanne Grinovero (JIRA)

Infinispan Query module should load entities using getAsync ----------------------------------------------------------- Key: ISPN-951 URL: https://issues.jboss.org/browse/ISPN-951 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.0.BETA1 Requires migration to new Loader API from Hibernate Search -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (ISPN-284) Streamed rehashing

by Manik Surtani (JIRA)

Streamed rehashing ------------------ Key: ISPN-284 URL: https://jira.jboss.org/jira/browse/ISPN-284 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.GA Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA Currently rehashing uses RPC which uses byte array representations of state. These could use streams, perhaps using JGroups' STREAMING_STATE_TRANSFER sockets, for greater performance and robustness. -- 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, 11 months

9
22
0 / 0

[JBoss JIRA] Created: (ISPN-956) Update RESTEasy version used by REST server

by Michal Linhard (JIRA)

Update RESTEasy version used by REST server ------------------------------------------- Key: ISPN-956 URL: https://issues.jboss.org/browse/ISPN-956 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Michal Linhard Assignee: Michal Linhard Priority: Minor Fix For: 4.2.1.FINAL, 5.0.0.BETA1 Update RESTEasy version (currently 2.0-beta-2) used by REST server to a stable one (2.0.1.GA or 2.1.0.GA). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (ISPN-1058) Add tests to verify virtual nodes distribution

by Pete Muir (JIRA)

Add tests to verify virtual nodes distribution ---------------------------------------------- Key: ISPN-1058 URL: https://issues.jboss.org/browse/ISPN-1058 Project: Infinispan Issue Type: Task Affects Versions: 5.0.0.BETA2 Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.0.0.CR1 Whilst virtual nodes are passing existing tests verifying Inifinispan works, we don't have any tests verifying how virtual nodes distribute data. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
12
0 / 0

[JBoss JIRA] Created: (ISPN-263) Handle JGroups MERGE events to help deal with split brains

by Manik Surtani (JIRA)

Handle JGroups MERGE events to help deal with split brains ---------------------------------------------------------- Key: ISPN-263 URL: https://jira.jboss.org/jira/browse/ISPN-263 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.GA JGroups already detects split brains and issues a callback. The cache layer needs to decide what to do. The idea is to implement a few canned policies (restart, wipe, etc) and allow custom handlers to be attached as well. Analogous to JBCACHE-471 -- 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

13 years

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-1065) Use a better mechanism to parse config files

by Manik Surtani (JIRA)

Use a better mechanism to parse config files -------------------------------------------- Key: ISPN-1065 URL: https://issues.jboss.org/browse/ISPN-1065 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 4.2.1.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final The current codebase heavily relies on JAXB to: 1. Generate a XSD schema from a Configuration bean 2. Generate a parser to use with an XML configuration This is known to be slow, and can significantly add to start up time: {quote} We did some analysis of our AS6 descriptor code which was using JAXB (800ms), compared to straight stax (10ms) {quote} A possible solution could be to still use JAXB to generate the schema, but to also write a Maven plugin which would generate a STAX parser based on the XSD schema and Configuration bean at build time. Infinispan would then use this STAX parser rather than a JAXB generated parser, which would be a lot faster. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

8
24
0 / 0

[JBoss JIRA] Created: (ISPN-385) Add idle timeout to memcached and hot rod servers.

by Galder Zamarreno (JIRA)

Add idle timeout to memcached and hot rod servers. -------------------------------------------------- Key: ISPN-385 URL: https://jira.jboss.org/jira/browse/ISPN-385 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Add an IdleStateHandler to memcached and hot rod servers so that idle connections can be closed automatically. This is necessary to handle error conditions such as cases where clients erroneously indicate the server that it needs to read 20 bytes but they only send 10 bytes. Without such handler, the server will carry on waiting for bytes forever. The handler will provide a defence mechanism for such cases. The timeout will be configurable via the command line. Besides, clients wanting to do some connection pooling will require to configure this accordingly in the server. In other words, there's hardly any point in having servers configured with idle timeout of 30 seconds and clients closing connections after 60 seconds of idle time. These two should be aligned accordingly. -- 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

13 years

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-555) Remote nodes should have a user cfg timeout before heuristic rollback

by Mircea Markus (JIRA)

Remote nodes should have a user cfg timeout before heuristic rollback --------------------------------------------------------------------- Key: ISPN-555 URL: https://jira.jboss.org/browse/ISPN-555 Project: Infinispan Issue Type: Feature Request Components: Transactions Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.1.0.BETA1 This is code in TransactionTable.StaleTransactionCleanup. This is because the failing might get restarted and it can finish the transaction in a coordinated, non-heuristic manner. -- 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

13 years

4
10
0 / 0

[JBoss JIRA] Created: (ISPN-465) HTTP session management for Tomcat

by Manik Surtani (JIRA)

HTTP session management for Tomcat ---------------------------------- Key: ISPN-465 URL: https://jira.jboss.org/browse/ISPN-465 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Session management plugin for Glassfish, to allow running Glassfish in non-clustered mode and having all clustering of session state managed by Infinispan. -- 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

13 years

3
6
0 / 0

[JBoss JIRA] Created: (ISPN-689) Read past EOF caused in Lucene Directory when Lucene flushes but doesn't close the segment

by Sanne Grinovero (JIRA)

Read past EOF caused in Lucene Directory when Lucene flushes but doesn't close the segment ------------------------------------------------------------------------------------------ Key: ISPN-689 URL: https://jira.jboss.org/browse/ISPN-689 Project: Infinispan Issue Type: Bug Components: Lucene Directory Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.2.0.BETA1, 4.2.0.Final, 5.0.0.Final While this is not the default access scenario performed by Lucene it's possible in some branches to flush the segment and be able to read it before the close. I could reproduce the following stacktrace in high load / huge sized index but not in a unit test; disabling the batching started between .flush() and .close() seems to resolve the issue; also this batch seems totally useless as I couldn't find any chance in performance when disabling it. java.io.IOException: Read past EOF: Chunk value could not be found for key _ni.fdt|4|issues at org.infinispan.lucene.InfinispanIndexInput.setBufferToCurrentChunk(InfinispanIndexInput.java:138) at org.infinispan.lucene.InfinispanIndexInput.nextChunk(InfinispanIndexInput.java:131) at org.infinispan.lucene.InfinispanIndexInput.readBytes(InfinispanIndexInput.java:96) at org.apache.lucene.store.IndexInput.readBytes(IndexInput.java:61) at org.apache.lucene.index.CompoundFileWriter.copyFile(CompoundFileWriter.java:228) at org.apache.lucene.index.CompoundFileWriter.close(CompoundFileWriter.java:184) at org.apache.lucene.index.IndexWriter.flushDocStores(IndexWriter.java:2342) at org.apache.lucene.index.IndexWriter.doFlushInternal(IndexWriter.java:4359) at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:4264) at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:4255) at org.apache.lucene.index.IndexWriter.prepareCommit(IndexWriter.java:4133) at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4206) at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4179) -- 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

13 years, 1 month

5
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2011