August 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4390) CHMv8 leaks ThreadLocal

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4390?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4390: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4505, https://github.com/infinispan/infinispan/pull/4506 (was: https://github.com/infinispan/infinispan/pull/4505) > CHMv8 leaks ThreadLocal > ----------------------- > > Key: ISPN-4390 > URL: https://issues.jboss.org/browse/ISPN-4390 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 8.2.5.Final > > > As discussed on: http://lists.jboss.org/pipermail/infinispan-dev/2014-June/015055.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4390) CHMv8 leaks ThreadLocal

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4390?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4390: ---------------------------------- Fix Version/s: (was: 8.1.5.Final) > CHMv8 leaks ThreadLocal > ----------------------- > > Key: ISPN-4390 > URL: https://issues.jboss.org/browse/ISPN-4390 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 8.2.5.Final > > > As discussed on: http://lists.jboss.org/pipermail/infinispan-dev/2014-June/015055.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4390) CHMv8 leaks ThreadLocal

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4390?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4390: ------------------------------------- Assignee: Tristan Tarrant (was: William Burns) > CHMv8 leaks ThreadLocal > ----------------------- > > Key: ISPN-4390 > URL: https://issues.jboss.org/browse/ISPN-4390 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 8.1.5.Final, 9.0.0.Final, 8.2.5.Final > > > As discussed on: http://lists.jboss.org/pipermail/infinispan-dev/2014-June/015055.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4390) CHMv8 leaks ThreadLocal

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4390?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4390: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4505 > CHMv8 leaks ThreadLocal > ----------------------- > > Key: ISPN-4390 > URL: https://issues.jboss.org/browse/ISPN-4390 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 8.1.5.Final, 9.0.0.Final, 8.2.5.Final > > > As discussed on: http://lists.jboss.org/pipermail/infinispan-dev/2014-June/015055.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6933) Rename the jdk8backported package as its name is confusing

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6933?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-6933: ------------------------------------- Assignee: Tristan Tarrant (was: William Burns) > Rename the jdk8backported package as its name is confusing > ---------------------------------------------------------- > > Key: ISPN-6933 > URL: https://issues.jboss.org/browse/ISPN-6933 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1 > > > As discussed on the mailing list on this thread, the package name of {{org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8}} (and others in the same package) is confusing as people keep wondering if we should get rid of it, if it's supposed to work on JDK7, etc.. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6933) Rename the jdk8backported package as its name is confusing

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6933?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6933: ---------------------------------- Status: Open (was: New) > Rename the jdk8backported package as its name is confusing > ---------------------------------------------------------- > > Key: ISPN-6933 > URL: https://issues.jboss.org/browse/ISPN-6933 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1 > > > As discussed on the mailing list on this thread, the package name of {{org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8}} (and others in the same package) is confusing as people keep wondering if we should get rid of it, if it's supposed to work on JDK7, etc.. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6933) Rename the jdk8backported package as its name is confusing

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6933?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6933: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4505 > Rename the jdk8backported package as its name is confusing > ---------------------------------------------------------- > > Key: ISPN-6933 > URL: https://issues.jboss.org/browse/ISPN-6933 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta1 > > > As discussed on the mailing list on this thread, the package name of {{org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8}} (and others in the same package) is confusing as people keep wondering if we should get rid of it, if it's supposed to work on JDK7, etc.. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6225) Allow the ratio segments/shard to be configurable for the AffinityIndexManager

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6225?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6225: ------------------------------------ Summary: Allow the ratio segments/shard to be configurable for the AffinityIndexManager (was: Allow the ratio segments/shard to be configurable for the ShardIndexManager) > Allow the ratio segments/shard to be configurable for the AffinityIndexManager > ------------------------------------------------------------------------------ > > Key: ISPN-6225 > URL: https://issues.jboss.org/browse/ISPN-6225 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > Currently it's fixed on 1:1 meaning every Infinispan segment will create a shard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6943) Upgrade to Hibernate HQL Parser version 1.3.0.Final

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6943?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6943: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. > Upgrade to Hibernate HQL Parser version 1.3.0.Final > ---------------------------------------------------- > > Key: ISPN-6943 > URL: https://issues.jboss.org/browse/ISPN-6943 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6947) Indexing mode not compatible with multiple entities per cache

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6947?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6947: ------------------------------------ Status: Open (was: New) > Indexing mode not compatible with multiple entities per cache > ------------------------------------------------------------- > > Key: ISPN-6947 > URL: https://issues.jboss.org/browse/ISPN-6947 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Gustavo Fernandes > > Consider a cache composed of two entities A and B, entity A is stored on RAM and entity B on Infinispan itself. The configuration to achieve that is below: > {noformat} > cacheCfg.indexing() > .index(Index.ALL) > .addIndexedEntity(A.class) > .addIndexedEntity(B.class) > .addProperty("A.directory_provider", "ram") > .addProperty("A.indexmanager", "org.infinispan.query.indexmanager.InfinispanIndexManager") > {noformat} > The configuration Index.ALL only makes sense to RAM directory, while for InfinispanIndexManager it'd cause redundant indexing. The indexing mode should not be at cache level but at "index" level -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2016