October 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4827) Add JMX attributes to inspect partition health

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4827?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4827: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2943 > Add JMX attributes to inspect partition health > ---------------------------------------------- > > Key: ISPN-4827 > URL: https://issues.jboss.org/browse/ISPN-4827 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Affects Versions: 7.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4829) OsgiClassLoader.getInstance() is not thread-safe

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-4829?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-4829: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2945 > OsgiClassLoader.getInstance() is not thread-safe > ------------------------------------------------ > > Key: ISPN-4829 > URL: https://issues.jboss.org/browse/ISPN-4829 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.CR1 > Reporter: Ion Savin > Assignee: Ion Savin > > org.infinispan.commons.util.OsgiClassLoader.getInstance() is using non-thread-safe lazy initialization. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4830) Inconsistent naming for the HotRod client Karaf features

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-4830?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-4830: ---------------------------- Status: Open (was: New) > Inconsistent naming for the HotRod client Karaf features > -------------------------------------------------------- > > Key: ISPN-4830 > URL: https://issues.jboss.org/browse/ISPN-4830 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Remote Protocols > Affects Versions: 7.0.0.CR1 > Reporter: Ion Savin > Assignee: Ion Savin > > The current feature names are 'hotrod-client' and 'hotrod-client-with-query' while the other feature names match the module name. > Rename them to 'infinispan-client-hotrod' and 'infinispan-client-hotrod-with-query' and deprecate the old ones. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4830) Inconsistent naming for the HotRod client Karaf features

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-4830?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-4830: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2944 > Inconsistent naming for the HotRod client Karaf features > -------------------------------------------------------- > > Key: ISPN-4830 > URL: https://issues.jboss.org/browse/ISPN-4830 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Remote Protocols > Affects Versions: 7.0.0.CR1 > Reporter: Ion Savin > Assignee: Ion Savin > > The current feature names are 'hotrod-client' and 'hotrod-client-with-query' while the other feature names match the module name. > Rename them to 'infinispan-client-hotrod' and 'infinispan-client-hotrod-with-query' and deprecate the old ones. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4829) OsgiClassLoader.getInstance() is not thread-safe

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-4829?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-4829: ---------------------------- Status: Open (was: New) > OsgiClassLoader.getInstance() is not thread-safe > ------------------------------------------------ > > Key: ISPN-4829 > URL: https://issues.jboss.org/browse/ISPN-4829 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.CR1 > Reporter: Ion Savin > Assignee: Ion Savin > > org.infinispan.commons.util.OsgiClassLoader.getInstance() is using non-thread-safe lazy initialization. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4818) Allow creation of Infinispan caches as OSGi managed service

by Ion Savin (JIRA)

[ https://issues.jboss.org/browse/ISPN-4818?page=com.atlassian.jira.plugin.... ] Ion Savin updated ISPN-4818: ---------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.CR2 Resolution: Done > Allow creation of Infinispan caches as OSGi managed service > ----------------------------------------------------------- > > Key: ISPN-4818 > URL: https://issues.jboss.org/browse/ISPN-4818 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.0.0.CR1 > Reporter: Ion Savin > Assignee: Ion Savin > Fix For: 7.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4830) Inconsistent naming for the HotRod client Karaf features

by Ion Savin (JIRA)

Ion Savin created ISPN-4830: ------------------------------- Summary: Inconsistent naming for the HotRod client Karaf features Key: ISPN-4830 URL: https://issues.jboss.org/browse/ISPN-4830 Project: Infinispan Issue Type: Enhancement Components: Core, Remote Protocols Affects Versions: 7.0.0.CR1 Reporter: Ion Savin Assignee: Ion Savin The current feature names are 'hotrod-client' and 'hotrod-client-with-query' while the other feature names match the module name. Rename them to 'infinispan-client-hotrod' and 'infinispan-client-hotrod-with-query' and deprecate the old ones. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4829) OsgiClassLoader.getInstance() is not thread-safe

by Ion Savin (JIRA)

Ion Savin created ISPN-4829: ------------------------------- Summary: OsgiClassLoader.getInstance() is not thread-safe Key: ISPN-4829 URL: https://issues.jboss.org/browse/ISPN-4829 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.0.0.CR1 Reporter: Ion Savin Assignee: Ion Savin org.infinispan.commons.util.OsgiClassLoader.getInstance() is using non-thread-safe lazy initialization. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4828) Increasing default internal thread pool size

by Matej Čimbora (JIRA)

Matej Čimbora created ISPN-4828: ----------------------------------- Summary: Increasing default internal thread pool size Key: ISPN-4828 URL: https://issues.jboss.org/browse/ISPN-4828 Project: Infinispan Issue Type: Enhancement Affects Versions: 7.0.0.CR1 Reporter: Matej Čimbora Assignee: Mircea Markus Using synchronous replication with high number of concurrent clients doing put() operations over a shared set of keys, lock-acquisition timeouts occur when various thread pools (internal, jgroups oob) do not have appropriate size. org.infinispan.util.concurrent.TimeoutException: Unable to acquire lock after [3 seconds] on key [key_00000000000003B4] for requestor [Thread[OOB-66,default,node03-12795,5,main]]! Lock held by [Thread[OOB-314,default,node03-12795,5,main]] [org.infinispan.interceptors.InvocationContextInterceptor] (Stressor-1) ISPN000136: Execution error org.infinispan.util.concurrent.TimeoutException: org.infinispan.util.concurrent.TimeoutException: Node node04-24454 timed out This applies to both transactional and non-transactional configuration. The problem can be mitigated by increasing Infinispan's internal thread pool size (defined for remoteCommandsExecutor, blockingBoundedQueueThreadPool). In order to improve user experience either: a) When needed, the size of the thread pool should be increased as the load increases b) The default values should be high enough to handle even significant load (in terms of number of concurrent clients per node) c) The documentation should describe how the end user should size the thread pools based on expected load on the system -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4753) Add oldValue, oldMetadata and retry flag to filter and converter for Cluster Listeners.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4753?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4753: ----------------------------------------------- Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1150232|https://bugzilla.redhat.com/show_bug.cgi?id=1150232] from POST to MODIFIED > Add oldValue, oldMetadata and retry flag to filter and converter for Cluster Listeners. > --------------------------------------------------------------------------------------- > > Key: ISPN-4753 > URL: https://issues.jboss.org/browse/ISPN-4753 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners > Affects Versions: 7.0.0.Beta2 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR1 > > > It has been brought up that the filter and converter provided for use with Cluster Listeners need to also have access to the previous value/metadata and if the operation was a retry operation to allow for proper behavior of continuous query and other types of implementations. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 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 October 2014