September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10620) BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and ignores overwriting

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10620?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10620: --------------------------------- Summary: BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and ignores overwriting (was: BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and also does not perform proper overwriting) > BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and ignores overwriting > -------------------------------------------------------------------------------------------------- > > Key: ISPN-10620 > URL: https://issues.jboss.org/browse/ISPN-10620 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > > The operations are held in a map keyed by name, so some overloaded operations like DefaultCahcheManager.startCache() and DefaultCahcheManager.startCache(String cacheName) are basically discarded unintentionally. > Also, the order of processing superclasses is wrong (reversed), so eventually overwritten operations are not correctly processed. The one in the superclass wins, so the overwrite is basically ignored. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10620) BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and also does not perform proper overwriting

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-10620: ------------------------------------ Summary: BasicComponentRegistryImpl.getMBeanMetadata discards overloaded operations and also does not perform proper overwriting Key: ISPN-10620 URL: https://issues.jboss.org/browse/ISPN-10620 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 10.0.0.CR1 Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 10.0.0.CR3 The operations are held in a map keyed by name, so some overloaded operations like DefaultCahcheManager.startCache() and DefaultCahcheManager.startCache(String cacheName) are basically discarded unintentionally. Also, the order of processing superclasses is wrong (reversed), so eventually overwritten operations are not correctly processed. The one in the superclass wins, so the overwrite is basically ignored. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10619) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10619: --------------------------------------- Summary: If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence Key: ISPN-10619 URL: https://issues.jboss.org/browse/ISPN-10619 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 10.0.0.CR2 Environment: Cache configuration with preload <local-cache name="default"> <persistence> <file-store shared="false" preload="true" fetch-state="true"/> </persistence> </local-cache> Reporter: Wolf-Dieter Fink If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. This works correct if the server is not restarted or preload=false for the store. If preload is enabled and the server preload the date the creationTime is set to the current server start time. In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-10618: --------------------------------------- Summary: If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence Key: ISPN-10618 URL: https://issues.jboss.org/browse/ISPN-10618 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 10.0.0.CR2 Environment: Cache configuration with preload <local-cache name="default"> <persistence> <file-store shared="false" preload="true" fetch-state="true"/> </persistence> </local-cache> Reporter: Wolf-Dieter Fink If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. This works correct if the server is not restarted or preload=false for the store. If preload is enabled and the server preload the date the creationTime is set to the current server start time. In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10615) MBean operation metadata is broken, param type and param description are swapped

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10615?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10615: --------------------------------- Sprint: DataGrid Sprint #34 > MBean operation metadata is broken, param type and param description are swapped > -------------------------------------------------------------------------------- > > Key: ISPN-10615 > URL: https://issues.jboss.org/browse/ISPN-10615 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10617) Docs: Getting started with k8s/OpenShift

by Donald Naro (Jira)

Donald Naro created ISPN-10617: ---------------------------------- Summary: Docs: Getting started with k8s/OpenShift Key: ISPN-10617 URL: https://issues.jboss.org/browse/ISPN-10617 Project: Infinispan Issue Type: Task Reporter: Donald Naro Assignee: Donald Naro assembly with getting started that includes procedure to setup pull request tokens -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10617) Docs: Getting started with k8s/OpenShift

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10617?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10617: ------------------------------- Component/s: Documentation-Servers > Docs: Getting started with k8s/OpenShift > ---------------------------------------- > > Key: ISPN-10617 > URL: https://issues.jboss.org/browse/ISPN-10617 > Project: Infinispan > Issue Type: Task > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > assembly with getting started that includes procedure to setup pull request tokens -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10616) Docs: Modularize Hot Rod transactions

by Donald Naro (Jira)

Donald Naro created ISPN-10616: ---------------------------------- Summary: Docs: Modularize Hot Rod transactions Key: ISPN-10616 URL: https://issues.jboss.org/browse/ISPN-10616 Project: Infinispan Issue Type: Enhancement Components: Documentation-Servers Reporter: Donald Naro Assignee: Donald Naro -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10615) MBean operation metadata is broken, param type and param description are swapped

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10615?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10615: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7315 > MBean operation metadata is broken, param type and param description are swapped > -------------------------------------------------------------------------------- > > Key: ISPN-10615 > URL: https://issues.jboss.org/browse/ISPN-10615 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9889) Docs: Inline JGroups Config

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-9889?page=com.atlassian.jira.plugin.... ] Donald Naro closed ISPN-9889. ----------------------------- Release Notes Text: inliine jgroups config covered as part of https://issues.jboss.org/browse/ISPN-10511 Resolution: Duplicate > Docs: Inline JGroups Config > --------------------------- > > Key: ISPN-9889 > URL: https://issues.jboss.org/browse/ISPN-9889 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Affects Versions: 10.0.0.Alpha2 > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Update Server Guide and docs for changes to inline JGroups config. > Relates to this PR: https://github.com/infinispan/infinispan/pull/6615 -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019