[JBoss JIRA] (ISPN-4783) Using new ArrayList<>(resultCache.values())
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4783?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4783:
-----------------------------------------------
William Burns <wburns(a)redhat.com> changed the Status of [bug 1160416|https://bugzilla.redhat.com/show_bug.cgi?id=1160416] from NEW to POST
> Using new ArrayList<>(resultCache.values())
> -------------------------------------------
>
> Key: ISPN-4783
> URL: https://issues.jboss.org/browse/ISPN-4783
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 6.0.2.Final, 7.0.0.CR2
> Reporter: Markus Vogt
> Assignee: William Burns
> Fix For: 7.0.0.Final
>
> Attachments: cacheConfig.xml, ISPN4783_Test.java
>
>
> Hi,
> I am a little bit confused about the behaviour of getting the values from a cache and inserting into an ArrayList.
> I've putted one value into a cache, so that cache.size() is returning 1. If i now use 'new ArrayList<>(resultCache.values())', there will be two items in the list.
> By iterating over the cache, only one iteration will run... Where comes the second item from?
> Regards,
> Markus
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4980) Leaking not shut down cache manager cause VM crash on JDK6 and skipping tests
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4980?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-4980:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1163782
> Leaking not shut down cache manager cause VM crash on JDK6 and skipping tests
> -----------------------------------------------------------------------------
>
> Key: ISPN-4980
> URL: https://issues.jboss.org/browse/ISPN-4980
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core, Test Suite - Query
> Affects Versions: 7.0.0.Final
> Environment: consistently failing with JDK6 (very rare occurences with JDK7)
> Reporter: Tomas Sykora
> Priority: Critical
> Labels: test
>
> Please, see linked Bugzilla for more infromation, it also contains links for console outputs from CI jobs and other information we were able to gather.
> Just very briefly, 2 most important meesages:
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!! (testng-ProtobufWrapperIndexingTest) Exiting because ProtobufWrapperIndexingTest has NOT shut down all the cache managers it has started !!!!!!!
> !!!!!! (testng-ProtobufWrapperIndexingTest) See allocation stacktrace to find out where still-running cacheManager (org.infinispan.manager.DefaultCacheManager@1e601e6@Address:null) was created: !!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test (default-test) on project infinispan-server-hotrod: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
> Occuring in:
> [INFO] Building Infinispan Remote Query Server
> [INFO] Building Infinispan Hot Rod Server
> [INFO] Building Infinispan JPA CacheStore
> modules
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4980) Leaking not shut down cache manager cause VM crash on JDK6 and skipping tests
by Tomas Sykora (JIRA)
Tomas Sykora created ISPN-4980:
----------------------------------
Summary: Leaking not shut down cache manager cause VM crash on JDK6 and skipping tests
Key: ISPN-4980
URL: https://issues.jboss.org/browse/ISPN-4980
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core, Test Suite - Query
Affects Versions: 7.0.0.Final
Environment: consistently failing with JDK6 (very rare occurences with JDK7)
Reporter: Tomas Sykora
Priority: Critical
Please, see linked Bugzilla for more infromation, it also contains links for console outputs from CI jobs and other information we were able to gather.
Just very briefly, 2 most important meesages:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!! (testng-ProtobufWrapperIndexingTest) Exiting because ProtobufWrapperIndexingTest has NOT shut down all the cache managers it has started !!!!!!!
!!!!!! (testng-ProtobufWrapperIndexingTest) See allocation stacktrace to find out where still-running cacheManager (org.infinispan.manager.DefaultCacheManager@1e601e6@Address:null) was created: !!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test (default-test) on project infinispan-server-hotrod: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.14.1:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
Occuring in:
[INFO] Building Infinispan Remote Query Server
[INFO] Building Infinispan Hot Rod Server
[INFO] Building Infinispan JPA CacheStore
modules
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (ISPN-4979) CacheStatusResponse map uses too much memory
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4979?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-4979:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1163573
> CacheStatusResponse map uses too much memory
> --------------------------------------------
>
> Key: ISPN-4979
> URL: https://issues.jboss.org/browse/ISPN-4979
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Dan Berindei
> Priority: Critical
> Fix For: 7.1.0.Final
>
>
> When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map on the new coordinator can get quite large. One of the problems that seems to be that the addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the deserialized version occupies more memory.
> We need to investigate why the objects are not "shared" by the River marshaller, and maybe work around the problem by de-duplicating the addresses in the externalizer.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months