January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11142) Spring Boot Starter for Infinispan 10.1

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11142?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11142: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Duplicate Issue > Spring Boot Starter for Infinispan 10.1 > --------------------------------------- > > Key: ISPN-11142 > URL: https://issues.redhat.com/browse/ISPN-11142 > Project: Infinispan > Issue Type: Component Upgrade > Components: Spring Integration > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10981) CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-10981?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10981: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures > --------------------------------------------------------------------------- > > Key: ISPN-10981 > URL: https://issues.redhat.com/browse/ISPN-10981 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 10.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.1.Final > > > {{CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess}} fails very often. > {noformat} > 17:34:36,699 ERROR [TestSuiteProgress] Test failed: CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess > java.lang.AssertionError: expected:<Hola World> but was:<null> > at org.junit.Assert.fail(Assert.java:88) ~[junit-4.12.jar:4.12] > at org.junit.Assert.failNotEquals(Assert.java:834) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:118) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:144) ~[junit-4.12.jar:4.12] > at org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess(CacheWriterTest.java:1047) ~[cache-tests-1.1.0-tests.jar:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11143) infinispan-component-annotations is missing from eap modules

by Gustavo Lira e Silva (Jira)

[ https://issues.redhat.com/browse/ISPN-11143?page=com.atlassian.jira.plugi... ] Gustavo Lira e Silva reassigned ISPN-11143: ------------------------------------------- Assignee: Pedro Ruivo > infinispan-component-annotations is missing from eap modules > ------------------------------------------------------------ > > Key: ISPN-11143 > URL: https://issues.redhat.com/browse/ISPN-11143 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.1.0.Final > Reporter: Gustavo Lira e Silva > Assignee: Pedro Ruivo > Priority: Major > > infinispan-component-annotations.jar is missing from eap modules -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11143) infinispan-component-annotations is missing from eap modules

by Gustavo Lira e Silva (Jira)

Gustavo Lira e Silva created ISPN-11143: ------------------------------------------- Summary: infinispan-component-annotations is missing from eap modules Key: ISPN-11143 URL: https://issues.redhat.com/browse/ISPN-11143 Project: Infinispan Issue Type: Bug Affects Versions: 10.1.0.Final Reporter: Gustavo Lira e Silva infinispan-component-annotations.jar is missing from eap modules -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11133) Server arguments are not applied to jgroups transport

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11133?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11133: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Server arguments are not applied to jgroups transport > ----------------------------------------------------- > > Key: ISPN-11133 > URL: https://issues.redhat.com/browse/ISPN-11133 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Server > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.1.Final > > > The server -b and -n arguments are not passed to the jgroups transport -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11131) server-runtime should use log4j2

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11131?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11131: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > server-runtime should use log4j2 > -------------------------------- > > Key: ISPN-11131 > URL: https://issues.redhat.com/browse/ISPN-11131 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.1.Final > > > Currently the server uses JBoss LogManager, because that's what the WildFly server used. > It works, but the properties-based configuration is kind of clunky: it uses almost the same format as {{java.util.logging}}, but there are differences. Also not many of our users are familiar with it: WildFly has its own logging configuration in the XML, and {{logging.properties}} is auto-generated. > It would be better if we switched to log4j2 with a {{java.util.logging}} bridge. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10981) CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-10981?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-10981: -------------------------------- Fix Version/s: 10.1.1.Final > CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures > --------------------------------------------------------------------------- > > Key: ISPN-10981 > URL: https://issues.redhat.com/browse/ISPN-10981 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 10.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.1.Final > > > {{CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess}} fails very often. > {noformat} > 17:34:36,699 ERROR [TestSuiteProgress] Test failed: CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess > java.lang.AssertionError: expected:<Hola World> but was:<null> > at org.junit.Assert.fail(Assert.java:88) ~[junit-4.12.jar:4.12] > at org.junit.Assert.failNotEquals(Assert.java:834) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:118) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:144) ~[junit-4.12.jar:4.12] > at org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess(CacheWriterTest.java:1047) ~[cache-tests-1.1.0-tests.jar:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10981) CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-10981?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-10981: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7729 > CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess random failures > --------------------------------------------------------------------------- > > Key: ISPN-10981 > URL: https://issues.redhat.com/browse/ISPN-10981 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 10.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.1.Final > > > {{CacheWriterTest.shouldWriteThoughUsingPutAll_partialSuccess}} fails very often. > {noformat} > 17:34:36,699 ERROR [TestSuiteProgress] Test failed: CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess > java.lang.AssertionError: expected:<Hola World> but was:<null> > at org.junit.Assert.fail(Assert.java:88) ~[junit-4.12.jar:4.12] > at org.junit.Assert.failNotEquals(Assert.java:834) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:118) ~[junit-4.12.jar:4.12] > at org.junit.Assert.assertEquals(Assert.java:144) ~[junit-4.12.jar:4.12] > at org.jsr107.tck.integration.CacheWriterTest.shouldWriteThroughRemoveAllSpecific_partialSuccess(CacheWriterTest.java:1047) ~[cache-tests-1.1.0-tests.jar:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11112) Make expiration non blocking

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11112?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11112: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.1.Final Resolution: Done > Make expiration non blocking > ---------------------------- > > Key: ISPN-11112 > URL: https://issues.redhat.com/browse/ISPN-11112 > Project: Infinispan > Issue Type: Enhancement > Components: Expiration > Reporter: Will Burns > Assignee: Will Burns > Priority: Critical > Fix For: 10.1.1.Final, 11.0.0.Final > > > Expiration today is inherently blocking due to living in the DataContainer. We need to move this elsewhere or refactor in such a way to let expiration be non blocking. Moving this to be non blocking will most likely highlight many other bugs in expiration code as our tests had no easy to do such things when everything was blocking (aka lots of random failures). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11112) Make expiration non blocking

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11112?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11112: -------------------------------- Status: Open (was: New) > Make expiration non blocking > ---------------------------- > > Key: ISPN-11112 > URL: https://issues.redhat.com/browse/ISPN-11112 > Project: Infinispan > Issue Type: Enhancement > Components: Expiration > Reporter: Will Burns > Assignee: Will Burns > Priority: Critical > Fix For: 10.1.1.Final, 11.0.0.Final > > > Expiration today is inherently blocking due to living in the DataContainer. We need to move this elsewhere or refactor in such a way to let expiration be non blocking. Moving this to be non blocking will most likely highlight many other bugs in expiration code as our tests had no easy to do such things when everything was blocking (aka lots of random failures). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020