March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11185) Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11185?page=com.atlassian.jira.plugi... ] Nistor Adrian closed ISPN-11185. -------------------------------- Fix Version/s: 10.1.5.Final 11.0.0.Alpha2 Resolution: Done > Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries > ------------------------------------------------------------------------------------ > > Key: ISPN-11185 > URL: https://issues.redhat.com/browse/ISPN-11185 > Project: Infinispan > Issue Type: Bug > Components: Analytics > Affects Versions: 10.0.1.Final, 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.5.Final, 11.0.0.Alpha2 > > > ISPN-11106 seems to assume that Infinispan is the only component using MicroProfile metrics. > However, ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. > At the very least, I need to be able to disable the logic in ApplicationMetricsRegistry.start(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11185) Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11185?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on ISPN-11185: -------------------------------------- As part of ISPN-11174 I did a major refactoring of Infinispan's mp metrics implementation and I also moved the registration of base and vendor metrics from infinispan's core to server. The server is indeed a standalone app, not a component, so this should be ok now. Users of infinispan embedded will not be bothered by this anymore. The fix is included in 10.1.5.Final. We can close this now. > Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries > ------------------------------------------------------------------------------------ > > Key: ISPN-11185 > URL: https://issues.redhat.com/browse/ISPN-11185 > Project: Infinispan > Issue Type: Bug > Components: Analytics > Affects Versions: 10.0.1.Final, 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Nistor Adrian > Priority: Major > > ISPN-11106 seems to assume that Infinispan is the only component using MicroProfile metrics. > However, ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. > At the very least, I need to be able to disable the logic in ApplicationMetricsRegistry.start(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11488) Operator Docs: Update info about external services

by Donald Naro (Jira)

Donald Naro created ISPN-11488: ---------------------------------- Summary: Operator Docs: Update info about external services Key: ISPN-11488 URL: https://issues.redhat.com/browse/ISPN-11488 Project: Infinispan Issue Type: Enhancement Components: Documentation Reporter: Donald Naro Assignee: Donald Naro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11487) Operator Docs: Add kubectl commands for community

by Donald Naro (Jira)

Donald Naro created ISPN-11487: ---------------------------------- Summary: Operator Docs: Add kubectl commands for community Key: ISPN-11487 URL: https://issues.redhat.com/browse/ISPN-11487 Project: Infinispan Issue Type: Enhancement Components: Documentation Reporter: Donald Naro Assignee: Donald Naro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11257) Indexed queries should automatically be broadcasted when needed

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11257?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11257: --------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Dev03 Resolution: Done Merged in master. Thanks [~gustavonalle]! > Indexed queries should automatically be broadcasted when needed > --------------------------------------------------------------- > > Key: ISPN-11257 > URL: https://issues.redhat.com/browse/ISPN-11257 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 11.0.0.Dev03 > > > Currently there is a parameter {{IndexedQueryMode}} with the values FETCH (local) or BROADCAST (clustered) for indexed queries. When omitted, Infinispan should automatically detect if the query should be local or not based on the configuration -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11486) Upgrade to javassist 3.26.0-GA

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11486?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11486: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8069 > Upgrade to javassist 3.26.0-GA > ------------------------------ > > Key: ISPN-11486 > URL: https://issues.redhat.com/browse/ISPN-11486 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11486) Upgrade to javassist 3.26.0-GA

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11486?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11486: --------------------------------- Fix Version/s: 11.0.0.Dev03 > Upgrade to javassist 3.26.0-GA > ------------------------------ > > Key: ISPN-11486 > URL: https://issues.redhat.com/browse/ISPN-11486 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11486) Upgrade to javassist 3.26.0-GA

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-11486: ------------------------------------ Summary: Upgrade to javassist 3.26.0-GA Key: ISPN-11486 URL: https://issues.redhat.com/browse/ISPN-11486 Project: Infinispan Issue Type: Component Upgrade Reporter: Nistor Adrian Assignee: Nistor Adrian -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11486) Upgrade to javassist 3.26.0-GA

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11486?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11486: --------------------------------- Status: Open (was: New) > Upgrade to javassist 3.26.0-GA > ------------------------------ > > Key: ISPN-11486 > URL: https://issues.redhat.com/browse/ISPN-11486 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11485) No Server logs after shutdownHook has been called

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11485?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11485: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8063 > No Server logs after shutdownHook has been called > ------------------------------------------------- > > Key: ISPN-11485 > URL: https://issues.redhat.com/browse/ISPN-11485 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha2, 10.1.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev03, 10.1.6.Final > > > When a server process receives a SIGTERM it simply logs the following, regardless of the log configuration: > {code} > INFO (Thread-0) [org.infinispan.SERVER] ISPN080002: Infinispan Server stopping > INFO (Thread-0) [org.infinispan.SERVER] ISPN080002: Infinispan Server stopped > {code} > This is because Log4j registers a shutdownHook with the runtime in order to cleanup log resources. In order to aid server debugging, we should [disable this shutdownHook|https://logging.apache.org/log4j/2.x/manual/configuration.html] and manually shutdown the Log4j LogManager. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020