March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10078) Core module should export reactive-streams for store implementations

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10078: ----------------------------------- Summary: Core module should export reactive-streams for store implementations Key: ISPN-10078 URL: https://issues.jboss.org/browse/ISPN-10078 Project: Infinispan Issue Type: Enhancement Components: Server, WildFly modules Affects Versions: 10.0.0.Beta2 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.Beta3, 9.4.11.Final As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10072?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10072: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6787, https://github.com/infinispan/infinispan/pull/6791 (was: https://github.com/infinispan/infinispan/pull/6787) > Core module should export reactive-streams for store implementations > -------------------------------------------------------------------- > > Key: ISPN-10072 > URL: https://issues.jboss.org/browse/ISPN-10072 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.11.Final > > > As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10072?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10072: -------------------------------- Fix Version/s: 9.4.11.Final > Core module should export reactive-streams for store implementations > -------------------------------------------------------------------- > > Key: ISPN-10072 > URL: https://issues.jboss.org/browse/ISPN-10072 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta3, 9.4.11.Final > > > As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10077) ClientSocketReadTimeoutTest.testPutTimeout fails

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10077: -------------------------------------- Summary: ClientSocketReadTimeoutTest.testPutTimeout fails Key: ISPN-10077 URL: https://issues.jboss.org/browse/ISPN-10077 Project: Infinispan Issue Type: Bug Components: Test Suite - Server Affects Versions: 9.4.10.Final, 10.0.0.Beta2 Environment: CI https://ci.infinispan.org/job/Infinispan/job/9.4.x/158/testReport/org.inf... Reporter: Tristan Tarrant Error Message Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 Stacktrace org.testng.TestException: Expected exception of type class java.net.SocketTimeoutException but got io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: syscall:getsockopt(..) failed: Connection refused: /127.0.0.1:11222 at io.netty.channel.unix.Socket.finishConnect(..)(Unknown Source) Caused by: io.netty.channel.unix.Errors$NativeConnectException: syscall:getsockopt(..) failed: Connection refused ... 1 more ... Removed 13 stack frames -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3643) Allow the listener to abort an transaction

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-3643?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3643: ------------------------------------ The behaviour was already implemented, see {{ListenerExceptionTest}}. I don't believe listeners are the best way to do validation though, because the listeners run both on the originator and on *all* the owners. In addition to doing more work, if the cache is transactional with 1PC or non-transactional, if the listener throws an exception on one of the owners will veto the change only on that owner. > Allow the listener to abort an transaction > ------------------------------------------ > > Key: ISPN-3643 > URL: https://issues.jboss.org/browse/ISPN-3643 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners, Transactions > Reporter: Mircea Markus > Assignee: William Burns > Priority: Major > > Two ways of doing this: > - listener throws an exception > - add an Event.abortTransaction()or Event.veto(false) on the listeners. > Discussed on the mailing list:http://markmail.org/message/y6enpffq3s4vb7fs -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10076) Non Blocking listeners event batching

by William Burns (Jira)

William Burns created ISPN-10076: ------------------------------------ Summary: Non Blocking listeners event batching Key: ISPN-10076 URL: https://issues.jboss.org/browse/ISPN-10076 Project: Infinispan Issue Type: Bug Components: Core Reporter: William Burns Assignee: William Burns A couple of places in ISPN-9614 were not written to utilize batching. These are linked at https://github.com/infinispan/infinispan/pull/6401#discussion_r267641437 https://github.com/infinispan/infinispan/pull/6401#discussion_r267665358 The former is definitely an issue to ensure memory doesn't run over, but the latter is less priority as the set should be empty or a very small fraction of the total data size. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10075) We should ensure that when CompletionStages are completed they are continued only on Infinispan threads

by William Burns (Jira)

William Burns created ISPN-10075: ------------------------------------ Summary: We should ensure that when CompletionStages are completed they are continued only on Infinispan threads Key: ISPN-10075 URL: https://issues.jboss.org/browse/ISPN-10075 Project: Infinispan Issue Type: Bug Components: Core Reporter: William Burns Fix For: 10.0.0.Final When a user can supply a CompletionStage to delay operations this can cause a possibility of that being completed on a different thread than expected. The new non blocking listeners will especially be affected by this (ISPN-9614). This is also problematic for CacheLoader SPI and any future API that takes a Publisher as an argument from the user. This issue should at least fix the upcoming non blocking listeners as discussed at https://github.com/infinispan/infinispan/pull/6401#issuecomment-475181484. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10020) PolarionJUnitXMLReporter assertion failure after configuration method failure

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10020?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10020: -------------------------------- Fix Version/s: 9.4.11.Final > PolarionJUnitXMLReporter assertion failure after configuration method failure > ----------------------------------------------------------------------------- > > Key: ISPN-10020 > URL: https://issues.jboss.org/browse/ISPN-10020 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.8.Final, 10.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.0.0.Beta3, 9.4.11.Final > > > {noformat} > 16:48:30,946 ERROR (testng-ExceptionEvictionTest:[]) [TestSuiteProgress] Test failed: org.infinispan.eviction.impl.ExceptionEvictionTest.testEntryExpirationOverwritten[DIST_SYNC, nodeCount=3, storageType=OFF_HEAP, optimisticTransaction=false] > java.lang.IllegalStateException: Duplicate test: org.infinispan.eviction.impl.ExceptionEvictionTest.testEntryExpirationOverwritten[DIST_SYNC, nodeCount=3, storageType=OFF_HEAP, optimisticTransaction=false] > at org.infinispan.commons.test.PolarionJUnitXMLReporter.checkDuplicatesAndAdd(PolarionJUnitXMLReporter.java:416) ~[infinispan-commons-test-10.0.0-SNAPSHOT.jar:10.0.0-SNAPSHOT] > at org.infinispan.commons.test.PolarionJUnitXMLReporter.onTestSkipped(PolarionJUnitXMLReporter.java:98) ~[infinispan-commons-test-10.0.0-SNAPSHOT.jar:10.0.0-SNAPSHOT] > at org.testng.internal.TestListenerHelper.runTestListeners(TestListenerHelper.java:61) [testng-6.14.3.jar:?] > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1389) [testng-6.14.3.jar:?] > at org.testng.internal.Invoker.registerSkippedTestResult(Invoker.java:1063) [testng-6.14.3.jar:?] > {noformat} > When TestNG skips a test method because a configuration method failed, it doesn't pass listeners the parameter values generated by the data provider, so {{PolarionJUnitXMLReporter}} can't generate a unique name for the test method execution. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10020) PolarionJUnitXMLReporter assertion failure after configuration method failure

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10020?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10020: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6737, https://github.com/infinispan/infinispan/pull/6790 (was: https://github.com/infinispan/infinispan/pull/6737) > PolarionJUnitXMLReporter assertion failure after configuration method failure > ----------------------------------------------------------------------------- > > Key: ISPN-10020 > URL: https://issues.jboss.org/browse/ISPN-10020 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.8.Final, 10.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.0.0.Beta3 > > > {noformat} > 16:48:30,946 ERROR (testng-ExceptionEvictionTest:[]) [TestSuiteProgress] Test failed: org.infinispan.eviction.impl.ExceptionEvictionTest.testEntryExpirationOverwritten[DIST_SYNC, nodeCount=3, storageType=OFF_HEAP, optimisticTransaction=false] > java.lang.IllegalStateException: Duplicate test: org.infinispan.eviction.impl.ExceptionEvictionTest.testEntryExpirationOverwritten[DIST_SYNC, nodeCount=3, storageType=OFF_HEAP, optimisticTransaction=false] > at org.infinispan.commons.test.PolarionJUnitXMLReporter.checkDuplicatesAndAdd(PolarionJUnitXMLReporter.java:416) ~[infinispan-commons-test-10.0.0-SNAPSHOT.jar:10.0.0-SNAPSHOT] > at org.infinispan.commons.test.PolarionJUnitXMLReporter.onTestSkipped(PolarionJUnitXMLReporter.java:98) ~[infinispan-commons-test-10.0.0-SNAPSHOT.jar:10.0.0-SNAPSHOT] > at org.testng.internal.TestListenerHelper.runTestListeners(TestListenerHelper.java:61) [testng-6.14.3.jar:?] > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1389) [testng-6.14.3.jar:?] > at org.testng.internal.Invoker.registerSkippedTestResult(Invoker.java:1063) [testng-6.14.3.jar:?] > {noformat} > When TestNG skips a test method because a configuration method failed, it doesn't pass listeners the parameter values generated by the data provider, so {{PolarionJUnitXMLReporter}} can't generate a unique name for the test method execution. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3643) Allow the listener to abort an transaction

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-3643?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-3643: ------------------------------------- This behavior once implemented should be made sure to be documented on the Listener interface, if is still exists. > Allow the listener to abort an transaction > ------------------------------------------ > > Key: ISPN-3643 > URL: https://issues.jboss.org/browse/ISPN-3643 > Project: Infinispan > Issue Type: Enhancement > Components: Listeners, Transactions > Reporter: Mircea Markus > Assignee: William Burns > Priority: Major > > Two ways of doing this: > - listener throws an exception > - add an Event.abortTransaction()or Event.veto(false) on the listeners. > Discussed on the mailing list:http://markmail.org/message/y6enpffq3s4vb7fs -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019