June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10274) Restructure the distributions

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10274?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10274: ----------------------------------- Sprint: ISPN+RHDG Sprint #29 > Restructure the distributions > ----------------------------- > > Key: ISPN-10274 > URL: https://issues.jboss.org/browse/ISPN-10274 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4 > > > * we drop infinispan--all, infinispan--minimal and infinispan-*-remote > * we keep infinispan-wildfly-modules-* > * we keep and rename the WildFly-based server to infinispan-wildfly-server-* (deprecated) > * infinispan-server-* is the new server > * we improve the docs to show how to use Maven, Gradle and Ivy > * an infinispan-tools zip which includes migrators, converters, etc -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10314) process_trace_logs.sh fails when a test method ends in "Test"

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10314?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10314: ----------------------------------- Sprint: ISPN+RHDG Sprint #29 > process_trace_logs.sh fails when a test method ends in "Test" > ------------------------------------------------------------- > > Key: ISPN-10314 > URL: https://issues.jboss.org/browse/ISPN-10314 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 10.0.0.Beta3, 9.4.14.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.0.0.Beta4 > > > When a method ends in {{Test}}, {{process_trace_logs.sh}} looks for a log with the method name + {{log.gz}}, and when it doesn't find the test log it stops searching for other test logs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9963) Restructure Documentation Titles

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9963?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9963: ---------------------------------- Sprint: JDG Sprint #25, JDG Sprint #27, ISPN+RHDG Sprint #29 (was: JDG Sprint #25, JDG Sprint #27) > Restructure Documentation Titles > -------------------------------- > > Key: ISPN-9963 > URL: https://issues.jboss.org/browse/ISPN-9963 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Restructure the layout of the documentation directory and set up new titles. Part 1 to adopt flexible customer content. > The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can be divided into sections and topics (discrete units of reusable information). > Also requires changes to the docs layout on the community website. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10070) DefaultCacheManager should stop components after start failure

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10070?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10070: ----------------------------------- Sprint: ISPN+RHDG Sprint #29 > DefaultCacheManager should stop components after start failure > -------------------------------------------------------------- > > Key: ISPN-10070 > URL: https://issues.jboss.org/browse/ISPN-10070 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.10.Final, 10.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.16.Final > > > Currently it is impossible to release all the resources allocated during startup if the {{DefaultCacheManager}} instance was created with {{start=true}}. The user has to do something like this: > {code:java} > DefaultCacheManager manager = new DefaultCacheManager(..., false); > try { > manager.start(); > } catch (Throwable t) { > manager.stop(); > throw t; > } > {code} > Both the constructor and the public {{start()}} method should clean up the started components after a startup failure, so that the user doesn't have to call {{stop()}} explicitly. > Our tests do not currently call {{stop()}} explicitly, so they leak threads and sockets when a manager fails to start (e.g. because something went wrong with the {{CONFIG}} cache). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10085) Hibernate51 and Hibernate53 should not report the same test name

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10085?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10085: ----------------------------------- Sprint: ISPN+RHDG Sprint #29 > Hibernate51 and Hibernate53 should not report the same test name > ---------------------------------------------------------------- > > Key: ISPN-10085 > URL: https://issues.jboss.org/browse/ISPN-10085 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.11.Final, 10.0.0.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > > infinispan-hibernate-cache-v51 and infinispan-hibernate-cache-v53 are using the same tests. Let's say that v51 run first and the test has one error. when running with v53, the test result will be overwritten in the "Test Result" Jenkins plugin because they have the same name, arguments and class name. > the example is here > https://ci.infinispan.org/job/Infinispan/job/PR-6731/13/testReport/org.in... > is it a test for v51 or v53? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9893) New Reactive API

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9893?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9893: ---------------------------------- Sprint: ISPN+RHDG Sprint #29 > New Reactive API > ---------------- > > Key: ISPN-9893 > URL: https://issues.jboss.org/browse/ISPN-9893 > Project: Infinispan > Issue Type: Enhancement > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > See sub-talks. This is an umbrella issue -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9946) ServerNG

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9946?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9946: ---------------------------------- Sprint: ISPN+RHDG Sprint #29 > ServerNG > -------- > > Key: ISPN-9946 > URL: https://issues.jboss.org/browse/ISPN-9946 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9721) Add non blocking Publisher for a Cache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9721?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9721: ---------------------------------- Sprint: ISPN+RHDG Sprint #29 > Add non blocking Publisher for a Cache > -------------------------------------- > > Key: ISPN-9721 > URL: https://issues.jboss.org/browse/ISPN-9721 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Publisher > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > We currently have distributed streams. Unfortunately this requires blocking to operate at various levels. We need to instead expose some sort of distributed publisher that allows for distributed operations but in a totally non blocking way. > I had started a branch that has some ideas for the public API https://github.com/wburns/infinispan/tree/ISPN-9565_publisher. I believe the use of the various compose methods should help reduce complexity as all of the operations can be in a utility class if needed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10309) Convert Remaining Parts to Non Blocking & Reduce Thread Pools

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10309?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10309: ----------------------------------- Sprint: ISPN+RHDG Sprint #29 > Convert Remaining Parts to Non Blocking & Reduce Thread Pools > ------------------------------------------------------------- > > Key: ISPN-10309 > URL: https://issues.jboss.org/browse/ISPN-10309 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > We would love to get our thread pools down to a single CPU thread pool (size = numCores) and a blocking thread pool (arbitrarily large). We may also require a scheduler pool for various options as well (limited size 1-2?). > To do this we need to remove remnants of our blocking code as possible. Possible issues for blocking are mostly around locks and io operations. > The persistence layer was completed with ISPN-9722 so that is not an issue. > The requirement around locking can be relaxed if the locks are guaranteed to be small in scope and do not wrap other blocking operations. An example would be a lock such as ones in CHM as long as we don't have large blocks for functional argument types. > If code cannot be made non blocking we must offload the operation to the blocking thread pool. Care must be taken to ensure that once the blocking portion of code is completed that we switch back the to CPU thread pool as soon as possible. The listener API for example is violating this and will run code in Infinispan from any thread that completes the listener that could be done from a user. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10313) EvictInvalidatedNearCacheTest.testEvictAfterReachingMax random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10313?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10313: ----------------------------------- Sprint: ISPN+RHDG Sprint #29 > EvictInvalidatedNearCacheTest.testEvictAfterReachingMax random failures > ----------------------------------------------------------------------- > > Key: ISPN-10313 > URL: https://issues.jboss.org/browse/ISPN-10313 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4 > > Attachments: ISPN-9599_globalcomponentregistry_permission_20190616-2133_EvictInvalidatedNearCacheTest-infinispan-client-hotrod.log.gz > > > From the log, it looks like the near cache may ignore put requests, and {{EvictInvalidatedNearCacheTest}} doesn't expect that: > {noformat} > 22:02:29,709 TRACE (testng-Test:[]) [RetryOnFailureOperation] About to start executing operation GetWithMetadataOperation{(default), key=[B0x034B00000002, flags=0} on [id: 0x2ca8c2fb, L:/127.0.0.1:40582 - R:127.0.0.1/127.0.0.1:33741] > 22:02:29,709 TRACE (testng-Test:[]) [Codec] [] Wrote header for messageId=5085 to PooledUnsafeDirectByteBuf(ridx: 0, widx: 13, cap: 21). Operation code: 0x1b(UNKNOWN). Flags: 0x0. Topology id: -1 > 22:02:29,710 TRACE (Test-Client-Async-108-1:[]) [HeaderDecoder] Response 5085 belongs to GetWithMetadataOperation{(default), key=[B0x034B00000002, flags=0} on [id: 0x2ca8c2fb, L:/127.0.0.1:40582 - R:127.0.0.1/127.0.0.1:33741] > 22:02:29,710 TRACE (Test-Client-Async-108-1:[]) [NearCacheService] Conditionally put key=2 and value=MetadataValueImpl [created=-1, lifespan=-1, lastUsed=-1, maxIdle=-1, getVersion()=2, getValue()=v1] if absent in near cache (listenerId=[B0xD532F51E0F6632E1..[16]) > 22:02:29,725 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.client.hotrod.near.EvictInvalidatedNearCacheTest.testEvictAfterReachingMax > java.lang.AssertionError: expected:<v1> but was:<null> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88) ~[testng-6.14.3.jar:?] > at org.infinispan.client.hotrod.near.AssertsNearCache.assertGetKeyValue(AssertsNearCache.java:235) ~[test-classes/:?] > at org.infinispan.client.hotrod.near.AssertsNearCache.expectNearGetValue(AssertsNearCache.java:130) ~[test-classes/:?] > at org.infinispan.client.hotrod.near.EvictInvalidatedNearCacheTest.testEvictAfterReachingMax(EvictInvalidatedNearCacheTest.java:39) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 June 2019