March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5085) Convert REST server to using RESTEasy's Netty container integration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5085?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5085: ---------------------------------------- http://docs.jboss.org/resteasy/docs/2.3.7.Final/userguide/html/RESTEasy_E... > Convert REST server to using RESTEasy's Netty container integration > ------------------------------------------------------------------- > > Key: ISPN-5085 > URL: https://issues.jboss.org/browse/ISPN-5085 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > REST server is currently based on RESTEasy which relies on having a web container underneath to do its job. So, we're depending on jbossweb/undertow to provide the container capabilities. Instead, we should switch to a Netty based container to better control our dependencies. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5262) StateTransfer considerably slow with sync indexing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5262?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5262: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1204938 > StateTransfer considerably slow with sync indexing > -------------------------------------------------- > > Key: ISPN-5262 > URL: https://issues.jboss.org/browse/ISPN-5262 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.2.0.Beta1 > > > The {{StateResponseCommand}} applies state sequentially, chunk by chunk. > The sequential cache population by a single thread does not take advantage of the index backend automatic batching capabilities when subjected to multiple threads and consequentially state transfer time can become prohibitive for large number of entries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5117) EmbeddedAllTest.testAllEmbeddedClustered fails with AssertionError on Solaris

by Vitalii Chepeliuk (JIRA)

[ https://issues.jboss.org/browse/ISPN-5117?page=com.atlassian.jira.plugin.... ] Vitalii Chepeliuk commented on ISPN-5117: ----------------------------------------- This is jgroups clustering issue. It looks like we need to change jgroups configuration a bit to form cluster on Solaris and HP-UX > EmbeddedAllTest.testAllEmbeddedClustered fails with AssertionError on Solaris > ----------------------------------------------------------------------------- > > Key: ISPN-5117 > URL: https://issues.jboss.org/browse/ISPN-5117 > Project: Infinispan > Issue Type: Bug > Affects Versions: 7.1.0.Alpha1 > Environment: Solaris > Reporter: Vitalii Chepeliuk > Assignee: Tristan Tarrant > Labels: testsuite_stability > > {noformat} > java.lang.AssertionError: expected:<value1> but was:<null> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.infinispan.all.embedded.EmbeddedAllTest.testAllEmbeddedClustered(EmbeddedAllTest.java:80) > {noformat} > *JENKINS JOB:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5298) HotRod millisecond precision for lifespan/maxidle

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5298?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-5298: ---------------------------------------- Ion, I'll email Greg to see what kind of timeline we can expect. > HotRod millisecond precision for lifespan/maxidle > ------------------------------------------------- > > Key: ISPN-5298 > URL: https://issues.jboss.org/browse/ISPN-5298 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 7.2.0.Alpha1 > Reporter: Ion Savin > > Currently lifespan/maxidle precision is SECONDS. > JSR-107 requires MILLISECONDS precision. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5251) Eviction configuration must be enforced in Near Caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5251?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5251: ----------------------------------- Status: Open (was: New) > Eviction configuration must be enforced in Near Caches > ------------------------------------------------------ > > Key: ISPN-5251 > URL: https://issues.jboss.org/browse/ISPN-5251 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If near cache is enabled, users should define the maximum number of elements to store in it. This is important to avoid clients running out of memory as a result of using near caching. In the current set up, when someone enables near caching, the local cache is unbounded. > The best approach is to force clients to define a maximum number of elements if enabling near caching. 0 would be unlimited. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5251) Eviction configuration must be enforced in Near Caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5251?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5251: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3330 > Eviction configuration must be enforced in Near Caches > ------------------------------------------------------ > > Key: ISPN-5251 > URL: https://issues.jboss.org/browse/ISPN-5251 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If near cache is enabled, users should define the maximum number of elements to store in it. This is important to avoid clients running out of memory as a result of using near caching. In the current set up, when someone enables near caching, the local cache is unbounded. > The best approach is to force clients to define a maximum number of elements if enabling near caching. 0 would be unlimited. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5251) Eviction configuration must be enforced in Near Caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5251?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5251: ----------------------------------- Fix Version/s: 7.2.0.Beta2 > Eviction configuration must be enforced in Near Caches > ------------------------------------------------------ > > Key: ISPN-5251 > URL: https://issues.jboss.org/browse/ISPN-5251 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If near cache is enabled, users should define the maximum number of elements to store in it. This is important to avoid clients running out of memory as a result of using near caching. In the current set up, when someone enables near caching, the local cache is unbounded. > The best approach is to force clients to define a maximum number of elements if enabling near caching. 0 would be unlimited. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5320) Use new bounded CHMv8 for Hot Rod client near caches

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-5320: -------------------------------------- Summary: Use new bounded CHMv8 for Hot Rod client near caches Key: ISPN-5320 URL: https://issues.jboss.org/browse/ISPN-5320 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 7.2.0.Final This implementation would perform better than the existing lock-based LinkedHashMap implementation (org.infinispan.client.hotrod.near.LinkedMapNearCache) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5319) TreeCache with concurrent puts becomes inconsistent

by Jeremy Stone (JIRA)

Jeremy Stone created ISPN-5319: ---------------------------------- Summary: TreeCache with concurrent puts becomes inconsistent Key: ISPN-5319 URL: https://issues.jboss.org/browse/ISPN-5319 Project: Infinispan Issue Type: Bug Affects Versions: 5.3.0.Final, 7.2.0.Final Reporter: Jeremy Stone Concurrent puts using tree cache api store data values in the tree but the structure of tree can become corrupted. Namely: node.getChildren() for a parent node might not include the child node even though the child node exists and has some data. This makes it difficult to reliably use the tree cache structure to mirror a corresponding tree-like business data structure (e.g. materialized from a database). This can be readily reproduced with a local cache. A unit test is attached to the referenced forum topic. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5298) HotRod millisecond precision for lifespan/maxidle

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5298?page=com.atlassian.jira.plugin.... ] Ion Savin edited comment on ISPN-5298 at 3/23/15 11:18 AM: ----------------------------------------------------------- The TCK issue opened: https://github.com/jsr107/jsr107tck/issues/76 . Based on the reply I think the tests might change to address the issue but not sure when. was (Author: isavin): The TCK issue opened: https://github.com/jsr107/jsr107tck/issues/76 > HotRod millisecond precision for lifespan/maxidle > ------------------------------------------------- > > Key: ISPN-5298 > URL: https://issues.jboss.org/browse/ISPN-5298 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 7.2.0.Alpha1 > Reporter: Ion Savin > > Currently lifespan/maxidle precision is SECONDS. > JSR-107 requires MILLISECONDS precision. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015