May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9196) Autoclose iterator when transaction completes

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9196?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9196: ------------------------------ Summary: Autoclose iterator when transaction completes (was: Autoclose iterator when transaction commits) > Autoclose iterator when transaction completes > --------------------------------------------- > > Key: ISPN-9196 > URL: https://issues.jboss.org/browse/ISPN-9196 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Pedro Ruivo > > Any iterator opened on a transactional cache within the scope of transaction should be closed when the transaction completes (incl. rollback by transaction reaper). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9195) Iterator leak when Hot Rod client crashes

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-9195?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-9195: ------------------------------ Labels: memory_leak (was: ) > Iterator leak when Hot Rod client crashes > ----------------------------------------- > > Key: ISPN-9195 > URL: https://issues.jboss.org/browse/ISPN-9195 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.3.0.Beta1 > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Labels: memory_leak > > When the client abruptly terminates, or simply does not close the iterator, iterator resources on server are not released. > Any such resources should be handles with lease-based expiration. Additionally we could remove the resources when the connection that established them is closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9195) Iterator leak when Hot Rod client crashes

by Radim Vansa (JIRA)

Radim Vansa created ISPN-9195: --------------------------------- Summary: Iterator leak when Hot Rod client crashes Key: ISPN-9195 URL: https://issues.jboss.org/browse/ISPN-9195 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 9.3.0.Beta1 Reporter: Radim Vansa Assignee: Gustavo Fernandes When the client abruptly terminates, or simply does not close the iterator, iterator resources on server are not released. Any such resources should be handles with lease-based expiration. Additionally we could remove the resources when the connection that established them is closed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9193) CollectionMapper forEach should delegate to actualCollection

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9193?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9193: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CollectionMapper forEach should delegate to actualCollection > ------------------------------------------------------------ > > Key: ISPN-9193 > URL: https://issues.jboss.org/browse/ISPN-9193 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.CR1 > > > CollectionMapper currently delegates forEach method to the stream instead of the underlying collection. This can cause issues since stream serializes the function across to be executed on all nodes. This should instead delegate to the actualCollection to allow for local operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9178) EntityCollectionInvalidationTest.testAll randomly failing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9178?page=com.atlassian.jira.plugin.... ] Work on ISPN-9178 started by Galder Zamarreño. ---------------------------------------------- > EntityCollectionInvalidationTest.testAll randomly failing > --------------------------------------------------------- > > Key: ISPN-9178 > URL: https://issues.jboss.org/browse/ISPN-9178 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.CR1, 9.3.0.Final > > > Failure: > {code} > [INFO] Running > org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest > [ERROR] Tests run: 12, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 7.655 s <<< FAILURE! - in org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest > [ERROR] testAll[nonstrict, REPL_SYNC](org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest) Time elapsed: 0.563 s <<< FAILURE! > java.lang.AssertionError: Contact#1 was in cache > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest.assertLoadedFromCache(EntityCollectionInvalidationTest.java:426) > at org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest.testAll(EntityCollectionInvalidationTest.java:171) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) > {code} > TRACE logs attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9178) EntityCollectionInvalidationTest.testAll randomly failing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9178?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9178: ----------------------------------- Status: Open (was: New) > EntityCollectionInvalidationTest.testAll randomly failing > --------------------------------------------------------- > > Key: ISPN-9178 > URL: https://issues.jboss.org/browse/ISPN-9178 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.CR1, 9.3.0.Final > > > Failure: > {code} > [INFO] Running > org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest > [ERROR] Tests run: 12, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 7.655 s <<< FAILURE! - in org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest > [ERROR] testAll[nonstrict, REPL_SYNC](org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest) Time elapsed: 0.563 s <<< FAILURE! > java.lang.AssertionError: Contact#1 was in cache > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest.assertLoadedFromCache(EntityCollectionInvalidationTest.java:426) > at org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest.testAll(EntityCollectionInvalidationTest.java:171) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) > {code} > TRACE logs attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9178) EntityCollectionInvalidationTest.testAll randomly failing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9178?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-9178: -------------------------------------- Assignee: Galder Zamarreño > EntityCollectionInvalidationTest.testAll randomly failing > --------------------------------------------------------- > > Key: ISPN-9178 > URL: https://issues.jboss.org/browse/ISPN-9178 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.CR1, 9.3.0.Final > > > Failure: > {code} > [INFO] Running > org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest > [ERROR] Tests run: 12, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 7.655 s <<< FAILURE! - in org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest > [ERROR] testAll[nonstrict, REPL_SYNC](org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest) Time elapsed: 0.563 s <<< FAILURE! > java.lang.AssertionError: Contact#1 was in cache > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest.assertLoadedFromCache(EntityCollectionInvalidationTest.java:426) > at org.infinispan.test.hibernate.cache.commons.functional.cluster.EntityCollectionInvalidationTest.testAll(EntityCollectionInvalidationTest.java:171) > 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) > {code} > TRACE logs attached. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-62) Topology handling leading to Buffer leak

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-62?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-62: --------------------------------- Fix Version/s: 0.5.0 > Topology handling leading to Buffer leak > ---------------------------------------- > > Key: HRJS-62 > URL: https://issues.jboss.org/browse/HRJS-62 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.4.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.5.0 > > > When a new topology is received, the client waits for that to be installed before pushing operation results to the client. The way the code works currently is leading to a Buffer leak. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-62) Topology handling leading to Buffer leak

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-62?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-62: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/js-client/pull/20 > Topology handling leading to Buffer leak > ---------------------------------------- > > Key: HRJS-62 > URL: https://issues.jboss.org/browse/HRJS-62 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.4.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.5.0 > > > When a new topology is received, the client waits for that to be installed before pushing operation results to the client. The way the code works currently is leading to a Buffer leak. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HRJS-61) Avoid leaking Buffer instances from data Socket callback

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/HRJS-61?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated HRJS-61: --------------------------------- Status: Open (was: New) > Avoid leaking Buffer instances from data Socket callback > -------------------------------------------------------- > > Key: HRJS-61 > URL: https://issues.jboss.org/browse/HRJS-61 > Project: Infinispan Javascript client > Issue Type: Bug > Affects Versions: 0.4.0 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 0.5.0 > > > Connection class keeps around a replayable buffer in case responses from server come in chunks. On data callback references it creating a closure. However, if there's nothing else to read, these buffers should be marked to null so that callback functions can be garbage collected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018