January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7365) Creating cache from a particular template fails

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7365: -------------------------------------- Summary: Creating cache from a particular template fails (was: Creating template from existing template fails in some cases) > Creating cache from a particular template fails > ----------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: 7365_stacktrace.txt, domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7365) Administration console - creating template from existing template fails in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7365: ------------------------------------------- Small correction. Creating a new template out of the above-mentioned template works but creating a new cache based on replicatedCacheAsTemplate does not. > Administration console - creating template from existing template fails in some cases > ------------------------------------------------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: 7365_stacktrace.txt, domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7365) Administration console - creating template from existing template fails in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7365: ----------------------------------------- Assignee: Vladimir Blagojevic (was: Tristan Tarrant) > Administration console - creating template from existing template fails in some cases > ------------------------------------------------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: 7365_stacktrace.txt, domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7365) Administration console - creating template from existing template fails in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7365: ------------------------------------------- [~rmacor] [~ryanemerson] and I have experienced similar issues. See ISPN-7348 and ISPN-7219 for more details. However, in this case, I believe the problem is related to either configuration itself or some internal wiring i.e how caches are created and started (with this particular configuration). I would suggest [~NadirX] take a look at this one as he can either diagnose the root cause rather soon or delegate to somehow who can. Based on the fact that a cache *cannot* be created from CLI using this configuration I am deselecting JIRA component (JMX and Console) delegating this one to Tristan. > Administration console - creating template from existing template fails in some cases > ------------------------------------------------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: 7365_stacktrace.txt, domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7365) Administration console - creating template from existing template fails in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7365: ----------------------------------------- Assignee: Tristan Tarrant (was: Vladimir Blagojevic) > Administration console - creating template from existing template fails in some cases > ------------------------------------------------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Tristan Tarrant > Attachments: 7365_stacktrace.txt, domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-6677 at 1/18/17 4:51 AM: ------------------------------------------------------------------ AFAICT, core relies on HikariCP for JDBC connections that should provide retry capability. For the other cache stores like Mongo, this is problably built on the driver. was (Author: gustavonalle): AFAICT, core relies on HikariCP for JDBC connections that should provide retry capability. For the other cache stores like Mongo, this isnpribably built on the driver. > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-6677: ----------------------------------------- AFAICT, core relies on HikariCP for JDBC connections that should provide retry capability. For the other cache stores like Mongo, this isnpribably built on the driver. > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7365) Administration console - creating template from existing template fails in some cases

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7365?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7365: -------------------------------------- Attachment: 7365_stacktrace.txt > Administration console - creating template from existing template fails in some cases > ------------------------------------------------------------------------------------- > > Key: ISPN-7365 > URL: https://issues.jboss.org/browse/ISPN-7365 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: 7365_stacktrace.txt, domain.xml > > > Use the attached configuration file to reproduce. > click on cache container -> configuration -> templates -> add new template -> set name newTemplate and base configuration: replicatedCacheAsTemplate -> click create > Result: > There is an error pop up with empty message "{}" > The template is created but the configuration is not copied. > Note: I'm not sure which part of replicatedCacheAsTemplate configuration is causing this issue, but it's not happening with every template. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6677: ------------------------------------------- Yes, retries are the only option. But I think we should implement reties in Core (this way we could use the same approach for both embedded and client server). WDYT? On Wed, Jan 18, 2017 at 10:27 AM, Gustavo Fernandes (JIRA) <issues(a)jboss.org > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6677) Deal with unavailable dependencies during startup

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6677?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6677: ------------------------------------------- Yes, retries are the only option. But I think we should implement reties in Core (this way we could use the same approach for both embedded and client server). WDYT? > Deal with unavailable dependencies during startup > ------------------------------------------------- > > Key: ISPN-6677 > URL: https://issues.jboss.org/browse/ISPN-6677 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Blocker > > In Kubernetes not all Pods start at the same time. It is perfectly possible to start first Infinispan and a bit later the database (in this configuration we are assuming that Infinispan has a dependency to DB). Note that this setup would fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 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 2017