March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6377) Rebalance start event does not include node info

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6377?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6377: ---------------------------------- Status: Open (was: New) > Rebalance start event does not include node info > ------------------------------------------------ > > Key: ISPN-6377 > URL: https://issues.jboss.org/browse/ISPN-6377 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6377) Rebalance start event does not include node info

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6377?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6377: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4129 > Rebalance start event does not include node info > ------------------------------------------------ > > Key: ISPN-6377 > URL: https://issues.jboss.org/browse/ISPN-6377 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6377) Rebalance start event does not include node info

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6377: ------------------------------------- Summary: Rebalance start event does not include node info Key: ISPN-6377 URL: https://issues.jboss.org/browse/ISPN-6377 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 8.2.0.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6376) Task information should return parameter names

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6376?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6376: ---------------------------------- Status: Open (was: New) > Task information should return parameter names > ---------------------------------------------- > > Key: ISPN-6376 > URL: https://issues.jboss.org/browse/ISPN-6376 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Scripts are already knowledgeable about parameter names. Extend this to tasks so that the names can be displayed in the console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6376) Task information should return parameter names

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6376?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6376: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4128 > Task information should return parameter names > ---------------------------------------------- > > Key: ISPN-6376 > URL: https://issues.jboss.org/browse/ISPN-6376 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Scripts are already knowledgeable about parameter names. Extend this to tasks so that the names can be displayed in the console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6376) Task information should return parameter names

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6376?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6376: ---------------------------------- Fix Version/s: 9.0.0.Final 9.0.0.Alpha1 > Task information should return parameter names > ---------------------------------------------- > > Key: ISPN-6376 > URL: https://issues.jboss.org/browse/ISPN-6376 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > Scripts are already knowledgeable about parameter names. Extend this to tasks so that the names can be displayed in the console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6376) Task information should return parameter names

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-6376: ------------------------------------- Summary: Task information should return parameter names Key: ISPN-6376 URL: https://issues.jboss.org/browse/ISPN-6376 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Tristan Tarrant Scripts are already knowledgeable about parameter names. Extend this to tasks so that the names can be displayed in the console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6375) Metaspace memory leak with infinispan

by Andrej Dmitrenko (JIRA)

Andrej Dmitrenko created ISPN-6375: -------------------------------------- Summary: Metaspace memory leak with infinispan Key: ISPN-6375 URL: https://issues.jboss.org/browse/ISPN-6375 Project: Infinispan Issue Type: Feature Request Components: Core Affects Versions: 8.1.2.Final Reporter: Andrej Dmitrenko Attachments: memory-analyzer.png I use infinispan for embedded cache and criteria query in cache. It is works great! I start infinispan in my application and call embeddedCacheManager.stop() at application destroy. I run my application in oracle weblogic 12.1.3 server. And after redeploy my application I see metaspace memory leak. I have checked heap dump in memory analizer. The cause in thread local variable threadCounterHashCode in org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$CounterHashCode class After undeploy aplication there is a thread which keep thread local reference to threadCounterHashCode, and threadCounterHashCode keep link to classloader and that's why classloader cannot be removed from metaspace memory. I cannot control this thread. I have got suggestion in forum to create ticket in JIRA (https://developer.jboss.org/message/952848) Please do something with class org.infinispan.commons.util.concurrent.jdk8backported.EquivalentConcurrentHashMapV8$CounterHashCode to avoid metaspace memory leak in cases when user does not control thread pool -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6340) Expose indexing statistics via DMR

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6340?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6340: -------------------------------- Fix Version/s: 9.0.0.Final 9.0.0.Alpha1 > Expose indexing statistics via DMR > ---------------------------------- > > Key: ISPN-6340 > URL: https://issues.jboss.org/browse/ISPN-6340 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6368) Race condition in InternalCacheRegistryImpl.registerInternalCache

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6368?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6368: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/4127 > Race condition in InternalCacheRegistryImpl.registerInternalCache > ----------------------------------------------------------------- > > Key: ISPN-6368 > URL: https://issues.jboss.org/browse/ISPN-6368 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.Final, 8.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.1.3.Final, 8.2.1.Final > > > Access to internalCaches set can cause race conditions and errors related to duplicate cache definitions can be mistakenly reported. > {code} > 17:51:40,668 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.disttestcache: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.disttestcache: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000358: A cache configuration named ___query_known_classes already exists. This cannot be configured externally by the user. > at org.infinispan.registry.impl.InternalCacheRegistryImpl.registerInternalCache(InternalCacheRegistryImpl.java:56) > at org.infinispan.registry.impl.InternalCacheRegistryImpl.registerInternalCache(InternalCacheRegistryImpl.java:49) > at org.infinispan.query.backend.QueryKnownClasses.startInternalCache(QueryKnownClasses.java:219) > at org.infinispan.query.backend.QueryKnownClasses.start(QueryKnownClasses.java:119) > at org.infinispan.query.backend.QueryInterceptor.start(QueryInterceptor.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:859) > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:628) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:617) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:542) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:238) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:849) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:635) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:585) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:451) > at org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.getCache(AbstractDelegatingEmbeddedCacheManager.java:133) > at org.infinispan.server.infinispan.SecurityActions$5.run(SecurityActions.java:130) > at org.infinispan.server.infinispan.SecurityActions$5.run(SecurityActions.java:127) > at org.infinispan.security.Security.doPrivileged(Security.java:76) > at org.infinispan.server.infinispan.SecurityActions.doPrivileged(SecurityActions.java:63) > at org.infinispan.server.infinispan.SecurityActions.startCache(SecurityActions.java:135) > at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:86) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016