July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7195) Configure JGroups transport for the container

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7195?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic resolved ISPN-7195. --------------------------------------- Resolution: Won't Fix This is a major undertaking and we don't have time and resources for it now. > Configure JGroups transport for the container > --------------------------------------------- > > Key: ISPN-7195 > URL: https://issues.jboss.org/browse/ISPN-7195 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > We should enable admins to configure JGroups transport one cache container level -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7657) Administration console - Indexing tab allows invalid configuration to be set

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7657?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7657: -------------------------------------- Status: Open (was: New) > Administration console - Indexing tab allows invalid configuration to be set > ---------------------------------------------------------------------------- > > Key: ISPN-7657 > URL: https://issues.jboss.org/browse/ISPN-7657 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR3 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Setting indexing for invalidation cache is not a valid configuration, but the console allows this configuration. > Part of the server log after restart: > ... > org.infinispan.commons.CacheConfigurationException: ISPN000273: Indexing can not be enabled on caches in Invalidation mode > ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7647) Administration console - eviction tab allows to set invalid options

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7647?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7647: -------------------------------------- Status: Open (was: New) > Administration console - eviction tab allows to set invalid options > ------------------------------------------------------------------- > > Key: ISPN-7647 > URL: https://issues.jboss.org/browse/ISPN-7647 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR3 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > The only valid option for memory based eviction is LRU. However, the console allows the user to set any eviction strategy which results in error after server restart: > org.infinispan.commons.CacheConfigurationException: Eviction cannot use memory based approximation with LIRS > I suggest we select LRU strategy and disable the dropdown when memory is set as an eviction type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7649) Administration console - transaction tab allows to set invalid options

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7649?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7649: -------------------------------------- Status: Open (was: New) > Administration console - transaction tab allows to set invalid options > ---------------------------------------------------------------------- > > Key: ISPN-7649 > URL: https://issues.jboss.org/browse/ISPN-7649 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR3 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > If a cache is set to distributed async mode, setting transactions to FULL_XA mode results in error after the cluster restart. The console shouldn't allow this combination. > Suggested solution - dropdown should display only valid options for transaction mode for the given cache. > (I'm not sure if this is the only invalid combination) > Server error: > ... > org.infinispan.commons.CacheConfigurationException: ISPN000441: Unsupported async cache mode 'DIST_ASYNC' for transactional caches > ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7642) Administration console - remote sites are not displayed correctly on cache container page

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7642?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7642: -------------------------------------- Status: Open (was: New) > Administration console - remote sites are not displayed correctly on cache container page > ----------------------------------------------------------------------------------------- > > Key: ISPN-7642 > URL: https://issues.jboss.org/browse/ISPN-7642 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Attachments: Screenshot-cacheContainer.png, Screenshot-detail-cache.png, clustered.xml > > > Have 2 caches each configured with a different remote site. > When you click on cache container, both remote sites are displayed on both cache cards. Clicking on a cache to see cache detail page shows correct remote site. Please see the attached screenshots. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7643) Coordinator status is unavailable in Infinispan cluster

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7643?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7643: -------------------------------------- Status: Open (was: New) > Coordinator status is unavailable in Infinispan cluster > ------------------------------------------------------- > > Key: ISPN-7643 > URL: https://issues.jboss.org/browse/ISPN-7643 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > It seems that Coordinator field uses JGroups Address class which can be displayed properly. Since we already have a Coordinator Address field, maybe the best way would be to remove this from JMX. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5820) Add JMX notification support for cluster events

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5820?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5820: -------------------------------------- Status: Open (was: New) > Add JMX notification support for cluster events > ----------------------------------------------- > > Key: ISPN-5820 > URL: https://issues.jboss.org/browse/ISPN-5820 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Dan Berindei > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7971: -------------------------------------- Status: Open (was: New) > Display a warning that changes in standalone mode are not persisted > ------------------------------------------------------------------- > > Key: ISPN-7971 > URL: https://issues.jboss.org/browse/ISPN-7971 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > > The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7963) Relocate Infinispan Hibernate cache provider

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7963?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7963: ----------------------------------- Component/s: Hibernate Cache > Relocate Infinispan Hibernate cache provider > -------------------------------------------- > > Key: ISPN-7963 > URL: https://issues.jboss.org/browse/ISPN-7963 > Project: Infinispan > Issue Type: Task > Components: Hibernate Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.0.Final, 9.1.0.CR2 > > > Relocate Infinispan Hibernate second-level cache implementation to the Infinispan repository. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7963) Relocate Infinispan Hibernate cache provider

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7963?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7963: ----------------------------------- Fix Version/s: 9.1.0.Final 9.1.0.CR2 > Relocate Infinispan Hibernate cache provider > -------------------------------------------- > > Key: ISPN-7963 > URL: https://issues.jboss.org/browse/ISPN-7963 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.1.0.Final, 9.1.0.CR2 > > > Relocate Infinispan Hibernate second-level cache implementation to the Infinispan repository. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017