March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8901) Document deploying custom merge policies on the server

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-8901?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink reassigned ISPN-8901: -------------------------------------- Assignee: Wolf-Dieter Fink (was: Ryan Emerson) > Document deploying custom merge policies on the server > ------------------------------------------------------ > > Key: ISPN-8901 > URL: https://issues.jboss.org/browse/ISPN-8901 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Affects Versions: 9.2.0.Final > Reporter: Ryan Emerson > Assignee: Wolf-Dieter Fink > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8901) Document deploying custom merge policies on the server

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/ISPN-8901?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink updated ISPN-8901: ----------------------------------- Status: Open (was: New) > Document deploying custom merge policies on the server > ------------------------------------------------------ > > Key: ISPN-8901 > URL: https://issues.jboss.org/browse/ISPN-8901 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Affects Versions: 9.2.0.Final > Reporter: Ryan Emerson > Assignee: Wolf-Dieter Fink > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8918) When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8918?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-8918: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5817 > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-8918 > URL: https://issues.jboss.org/browse/ISPN-8918 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final, 9.2.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration. > The problem is that org/infinispan/factories/ComponentRegistry.java:77 is only called once the cache is being wired thus {{registerComponent(configuration, Configuration.class);}} is the only place where the configuration is put into the registry. > The best solution is to remove the cache in TERMINATED state once configuration is undefined thus establishing a clear terminal lifecycle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8918) When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8918?page=com.atlassian.jira.plugin.... ] Work on ISPN-8918 started by Radoslav Husar. -------------------------------------------- > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-8918 > URL: https://issues.jboss.org/browse/ISPN-8918 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final, 9.2.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration. > The problem is that org/infinispan/factories/ComponentRegistry.java:77 is only called once the cache is being wired thus {{registerComponent(configuration, Configuration.class);}} is the only place where the configuration is put into the registry. > The best solution is to remove the cache in TERMINATED state once configuration is undefined thus establishing a clear terminal lifecycle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8918) When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8918?page=com.atlassian.jira.plugin.... ] Radoslav Husar reassigned ISPN-8918: ------------------------------------ Assignee: Radoslav Husar > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-8918 > URL: https://issues.jboss.org/browse/ISPN-8918 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final, 9.2.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration. > The problem is that org/infinispan/factories/ComponentRegistry.java:77 is only called once the cache is being wired thus {{registerComponent(configuration, Configuration.class);}} is the only place where the configuration is put into the registry. > The best solution is to remove the cache in TERMINATED state once configuration is undefined thus establishing a clear terminal lifecycle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8918) When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8918?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-8918: --------------------------------- Status: Open (was: New) > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-8918 > URL: https://issues.jboss.org/browse/ISPN-8918 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final, 9.2.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration. > The problem is that org/infinispan/factories/ComponentRegistry.java:77 is only called once the cache is being wired thus {{registerComponent(configuration, Configuration.class);}} is the only place where the configuration is put into the registry. > The best solution is to remove the cache in TERMINATED state once configuration is undefined thus establishing a clear terminal lifecycle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8918) When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration

by Radoslav Husar (JIRA)

Radoslav Husar created ISPN-8918: ------------------------------------ Summary: When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration Key: ISPN-8918 URL: https://issues.jboss.org/browse/ISPN-8918 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.2.0.Final, 9.1.6.Final Reporter: Radoslav Husar When a cache is stopped and restarted, its configuration reference within component registry is not refreshed with defineConfiguration/undefineConfiguration. The problem is that org/infinispan/factories/ComponentRegistry.java:77 is only called once the cache is being wired thus {{registerComponent(configuration, Configuration.class);}} is the only place where the configuration is put into the registry. The best solution is to remove the cache in TERMINATED state once configuration is undefined thus establishing a clear terminal lifecycle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8913) Provide sha1 checksums for Infinispan downloads

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8913?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on ISPN-8913: -------------------------------------- What I would like to see is PGP signed checksums or at least checksums served over SSL-enabled website. > Provide sha1 checksums for Infinispan downloads > ----------------------------------------------- > > Key: ISPN-8913 > URL: https://issues.jboss.org/browse/ISPN-8913 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Affects Versions: 9.2.0.Final > Reporter: Ryan Emerson > > Currently infinispan.org only provides users with download links for our various distribution zips, in the future we should provide these alongside their respective sha1 checksums. The website will need to be updated to include a means of displaying this information, as well as the web site release scripts to automatically populate said information. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8893) Stack trace of a primary request of Infinispan is lost, damaging supportability severely

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ISPN-8893?page=com.atlassian.jira.plugin.... ] Yeray Borges updated ISPN-8893: ------------------------------- Status: Open (was: New) > Stack trace of a primary request of Infinispan is lost, damaging supportability severely > ---------------------------------------------------------------------------------------- > > Key: ISPN-8893 > URL: https://issues.jboss.org/browse/ISPN-8893 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Yeray Borges > Assignee: Yeray Borges > Labels: top-50-list > > A request is handled by XNIO's "default task-NNN" thread. If the request executes a clustering cache operation, like session replication, it waits for the backup operation on another server. And if the other server failed on the backup operation, the primary server unwraps the exception to print only the remote exception. The original context of thread "default task-NNN" is lost and a user can't even identify what the primary operation was. > This affects supportability too much. It seems only JDG 7.1 is free from this issue (it has {{AsyncInterceptorChain}}). All other releases like EAP 7.1, RHSSO which is based on EAP 7.0 has this issue. > See the "Forum Reference" link of a mail thread for the detail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8893) Stack trace of a primary request of Infinispan is lost, damaging supportability severely

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/ISPN-8893?page=com.atlassian.jira.plugin.... ] Yeray Borges updated ISPN-8893: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5815, https://github.com/infinispan/infinispan/pull/5816 (was: https://github.com/infinispan/infinispan/pull/5815) > Stack trace of a primary request of Infinispan is lost, damaging supportability severely > ---------------------------------------------------------------------------------------- > > Key: ISPN-8893 > URL: https://issues.jboss.org/browse/ISPN-8893 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Yeray Borges > Assignee: Yeray Borges > Labels: top-50-list > > A request is handled by XNIO's "default task-NNN" thread. If the request executes a clustering cache operation, like session replication, it waits for the backup operation on another server. And if the other server failed on the backup operation, the primary server unwraps the exception to print only the remote exception. The original context of thread "default task-NNN" is lost and a user can't even identify what the primary operation was. > This affects supportability too much. It seems only JDG 7.1 is free from this issue (it has {{AsyncInterceptorChain}}). All other releases like EAP 7.1, RHSSO which is based on EAP 7.0 has this issue. > See the "Forum Reference" link of a mail thread for the detail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018