[JBoss JIRA] (ISPN-1980) Distributed Queries problem when results size could be greater than HsQuery.maxResults
by Israel Lacerra (JIRA)
Israel Lacerra created ISPN-1980:
------------------------------------
Summary: Distributed Queries problem when results size could be greater than HsQuery.maxResults
Key: ISPN-1980
URL: https://issues.jboss.org/browse/ISPN-1980
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 5.1.4.CR1
Reporter: Israel Lacerra
Assignee: Sanne Grinovero
When a distributed query could get more results than HSQuery.maxResults, an exception is thrown:
Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 200, Size: 200
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at org.infinispan.query.clustered.DistributedIterator.current(DistributedIterator.java:140)
at org.infinispan.query.clustered.DistributedIterator.next(DistributedIterator.java:116)
The correct behaviour is to limit the results up to HsQuery.maxResults
--
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, 7 months
[JBoss JIRA] (ISPN-2015) Upgrade to Netty 3.4.2 when ready
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-2015:
--------------------------------------
Summary: Upgrade to Netty 3.4.2 when ready
Key: ISPN-2015
URL: https://issues.jboss.org/browse/ISPN-2015
Project: Infinispan
Issue Type: Component Upgrade
Components: Cache Server
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
According to Norman, there's some important memory optimisations coming in this version, that should in theory allow us to get rid of the custom replaying decoder.
I'll do the upgrade in a separate branch and I'll pass on to QE to run:
* Data stress tests and compare with current version
* Client stress tests and compare with native Memcached and previous versions
Depending on the results of this, we can potentially consider doing the upgrade in 5.1.x.
--
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, 7 months
[JBoss JIRA] (ISPN-1740) Refactor internal classes and SPIs to use new Configuration beans
by Manik Surtani (JIRA)
Manik Surtani created ISPN-1740:
-----------------------------------
Summary: Refactor internal classes and SPIs to use new Configuration beans
Key: ISPN-1740
URL: https://issues.jboss.org/browse/ISPN-1740
Project: Infinispan
Issue Type: Enhancement
Components: Configuration
Affects Versions: 5.1.0.FINAL
Reporter: Manik Surtani
Assignee: Vladimir Blagojevic
Fix For: 5.2.0.FINAL
The current programmatic configuration makes use of the old 5.0.x config beans internally (injection) as well as unit tests and in SPIs (CacheStore, CommandInterceptor, etc).
We need to refactor these SPIs and internal code to use the new post-5.1 config beans.
However, the public API (DefaultCacheManager) should still support the old Configuration beans. To do this we'd need to write something like the reverse of the LegacyConfigurationAdapter. The LegacyConfigurationAdapter takes a 5.1 Configuration and creates a 5.0 Configuration. We need to do this in reverse once the internals start using the new 5.1 Configuration.
--
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, 7 months