January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11123) Integrate Mutiny in the new api

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11123?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11123: -------------------------------- Summary: Integrate Mutiny in the new api (was: Integrate Mutinity in the new api) > Integrate Mutiny in the new api > ------------------------------- > > Key: ISPN-11123 > URL: https://issues.redhat.com/browse/ISPN-11123 > Project: Infinispan > Issue Type: Feature Request > Components: API > Affects Versions: 10.1.0.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: api > > Mutinity API has been released in the first version. > Upgrade the new reactive api to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11131?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11131: -------------------------------- Status: Open (was: New) > 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)

4 years, 11 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11131?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11131: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7726 > 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)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11116) Invalidation commands should not load the previous value from the store

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11116?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11116: ----------------------------------- Fix Version/s: 9.3.8.Final (was: 9.3.7.Final) > Invalidation commands should not load the previous value from the store > ----------------------------------------------------------------------- > > Key: ISPN-11116 > URL: https://issues.redhat.com/browse/ISPN-11116 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.6.Final, 9.4.17.Final, 10.0.1.Final, 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.3.8.Final, 11.0.0.Final, 9.4.18.Final, 10.1.1.Final > > > {{CacheLoaderInterceptor.visitInvalidateCommand()}} loads the previous value from the store, just in case there is a {{CacheEntryInvalidated}} listener that needs the previous value. This makes invalidation mode with a shared store very costly: for every write, every node receives an invalidation command, every node reads the value from the store, and then discards it. > But {{InvalidateCommand}} only removes entries from memory, it never removes entry from stores (either shared or private). If we don't load the previous value in the data container, there is nothing for the {{InvalidateCommand}} to do. No invalidated entry means no listener notifications, so we don't need to load the previous value or to change the behaviour of {{CacheEntryInvalidatedEvent}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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.redhat.com/browse/ISPN-10085?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-10085: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.1.Final Resolution: Done > Hibernate51 and Hibernate53 should not report the same test name > ---------------------------------------------------------------- > > Key: ISPN-10085 > URL: https://issues.redhat.com/browse/ISPN-10085 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.4.11.Final, 10.0.0.Final, 10.1.0.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > Fix For: 10.1.1.Final > > > 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.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11134) Upgrade Jackson to version 2.9.10

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11134?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11134: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade Jackson to version 2.9.10 > --------------------------------- > > Key: ISPN-11134 > URL: https://issues.redhat.com/browse/ISPN-11134 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.4.17.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.18.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11136) Docs: use imagedir asciidoc

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11136?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11136: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.1.Final Resolution: Done > Docs: use imagedir asciidoc > --------------------------- > > Key: ISPN-11136 > URL: https://issues.redhat.com/browse/ISPN-11136 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.1.Final > > > We should be setting the location of docs with imagedir as per: https://asciidoctor.org/docs/user-manual/#setting-the-location-of-images > I didn't know you could set ":imagesdir: path" in the main file and it applies to every image target. This makes things cleaner. > Need to add "imagesdir" to each .asciidoc for generating individual titles and /documentation/pom.xml for building all titles with maven. > Also fix a broken image in the cache modes comparison topic. Break after "+" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11136) Docs: use imagedir asciidoc

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11136?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11136: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7724 > Docs: use imagedir asciidoc > --------------------------- > > Key: ISPN-11136 > URL: https://issues.redhat.com/browse/ISPN-11136 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > We should be setting the location of docs with imagedir as per: https://asciidoctor.org/docs/user-manual/#setting-the-location-of-images > I didn't know you could set ":imagesdir: path" in the main file and it applies to every image target. This makes things cleaner. > Need to add "imagesdir" to each .asciidoc for generating individual titles and /documentation/pom.xml for building all titles with maven. > Also fix a broken image in the cache modes comparison topic. Break after "+" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11136) Docs: use imagedir asciidoc

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11136?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11136: ----------------------------------- Status: Open (was: New) > Docs: use imagedir asciidoc > --------------------------- > > Key: ISPN-11136 > URL: https://issues.redhat.com/browse/ISPN-11136 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > We should be setting the location of docs with imagedir as per: https://asciidoctor.org/docs/user-manual/#setting-the-location-of-images > I didn't know you could set ":imagesdir: path" in the main file and it applies to every image target. This makes things cleaner. > Need to add "imagesdir" to each .asciidoc for generating individual titles and /documentation/pom.xml for building all titles with maven. > Also fix a broken image in the cache modes comparison topic. Break after "+" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11115) Infinispan BOM should only have dependency management for its own artifacts

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11115?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11115: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Infinispan BOM should only have dependency management for its own artifacts > --------------------------------------------------------------------------- > > Key: ISPN-11115 > URL: https://issues.redhat.com/browse/ISPN-11115 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.0.Final > Reporter: Stéphane Nicoll > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.1.Final > > > A BOM should usually have dependency management for the artifacts of the project. Any attempt to provide dependency management for third party artifacts can lead to clashes and warnings in Maven when two boms compete for the same artifact. > Could you please consider removing dependency management for the transaction and cache API please? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020