July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7927) User Interface to manage Cluster Counters

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-7927?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-7927: ---------------------------------- Assignee: Vladimir Blagojevic > User Interface to manage Cluster Counters > ----------------------------------------- > > Key: ISPN-7927 > URL: https://issues.jboss.org/browse/ISPN-7927 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > > Implement operations to create and manage clustered counters -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7831) Administration console - adjust node memory graph to match PatternFly widget

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-7831?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-7831: ------------------------------- Priority: Minor (was: Major) > Administration console - adjust node memory graph to match PatternFly widget > ----------------------------------------------------------------------------- > > Key: ISPN-7831 > URL: https://issues.jboss.org/browse/ISPN-7831 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7276) Console should automatically logout on Server mode change

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-7276?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-7276: ------------------------------- Priority: Minor (was: Major) > Console should automatically logout on Server mode change > --------------------------------------------------------- > > Key: ISPN-7276 > URL: https://issues.jboss.org/browse/ISPN-7276 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 9.0.0.Alpha4 > Reporter: Ryan Emerson > Assignee: Vladimir Blagojevic > Priority: Minor > > Currently if a user does not logout of the console and then restarts the server(s) in a different mode, i.e. previously it was in domain and now standalone, when the user returns to the console nothing happens on page refresh. At present this means that the user must navigate to /logout or make sure the browser session has been cleared in order to login and use the console again. > We should handle this situation more gracefully: > Ideally the console should adapt to the new server mode upon page refresh (or even after x amount of time) and inform the user that the console has refreshed. In some cases this would involve transitioning to a new page if the current page does not exist in the new server mode. > At the very least, the console should automatically logout the user upon detecting that the server mode has changed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7224) Support synchronous get in Spring's cache abstraction

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7224?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7224: -------------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/5262 (was: https://github.com/infinispan/infinispan/pull/4695) > Support synchronous get in Spring's cache abstraction > ----------------------------------------------------- > > Key: ISPN-7224 > URL: https://issues.jboss.org/browse/ISPN-7224 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Stéphane Nicoll > Assignee: Sebastian Łaskawiec > Priority: Critical > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > Spring Framework 4.3 has introduced a read-through option See https://jira.spring.io/browse/SPR-9254 for more details. In practice this would require you to compile against 4.3 and implement the additional method. > The code is meant to be backward compatible with previous version, as long as you're guarding the new exception in an inner class, see [this implementation for an example|https://github.com/hazelcast/hazelcast/blob/37ba79c4a8d35617c5f6a...] > Let me know if I can help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8007) Consolidate logging of binary data

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8007?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8007: ------------------------------- Description: Provide more consistent binary data logging for clients and server. The primary method for logging binary data so far was {{Util.printArray}} and related methods that printed binary data in straight hex format, e.g. {code} Body value: 0304380000001 {code} In ISPN-7517, Dan added a new way of representing binary data with the added benefit that ascii data is represented as ascii, making it easier to debug things like cache names, e.g. {code} Decode buffer (32768)...\R\Y\_\A\S\P\_\A\D\M\I\N\>17\S\e\t\ \G\o\o\g\l\e\-\A\n\y\l\y\t\i {code} This latter method can be easier to deal with compared with previous method. We should convert all code to the same logging mechanisms so that it's easier to trace things. was: Provide more consistent binary data logging for clients and server. The primary method for logging binary data so far was {{{Util.printArray}}} and related methods that printed binary data in straight hex format, e.g. {code} Body value: 0304380000001 {code} In ISPN-7517, Dan added a new way of representing binary data with the added benefit that ascii data is represented as ascii, making it easier to debug things like cache names, e.g. {code} Decode buffer (32768)...\R\Y\_\A\S\P\_\A\D\M\I\N\>17\S\e\t\ \G\o\o\g\l\e\-\A\n\y\l\y\t\i {code} This latter method can be easier to deal with compared with previous method. We should convert all code to the same logging mechanisms so that it's easier to trace things. > Consolidate logging of binary data > ---------------------------------- > > Key: ISPN-8007 > URL: https://issues.jboss.org/browse/ISPN-8007 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > > Provide more consistent binary data logging for clients and server. > The primary method for logging binary data so far was {{Util.printArray}} and related methods that printed binary data in straight hex format, e.g. > {code} > Body value: 0304380000001 > {code} > In ISPN-7517, Dan added a new way of representing binary data with the added benefit that ascii data is represented as ascii, making it easier to debug things like cache names, e.g. > {code} > Decode buffer (32768)...\R\Y\_\A\S\P\_\A\D\M\I\N\>17\S\e\t\ \G\o\o\g\l\e\-\A\n\y\l\y\t\i > {code} > This latter method can be easier to deal with compared with previous method. > We should convert all code to the same logging mechanisms so that it's easier to trace things. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8008) Add Fault-tolerance to write-behind stores

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-8008: ---------------------------------- Summary: Add Fault-tolerance to write-behind stores Key: ISPN-8008 URL: https://issues.jboss.org/browse/ISPN-8008 Project: Infinispan Issue Type: Enhancement Components: Loaders and Stores Reporter: Ryan Emerson Assignee: Ryan Emerson Currently when a store is configured to be write-behind, three attempts are made to write the queued modifications to the store. If all three attempts fail, then this error is simply logged and the modifications are never written to the store. We should allow users to configure a write-behind store so that: In the event that a write-behind fails, further operations on the cache are not allowed and the modifications which failed to write to the store are queued indefinitely. Once the underlying store becomes available, the queued modifications should be written and then the cache should become available. To determine whether a store has become available again, the AsyncCacheWriter will have to poll the store's availability. Currently the CacheWriter interface does not allow such behaviour, therefore there are two options: * Attempt a write and catch an exception if the store is not currently available * Add a method to return the current status of a store to the CacheWriter interface -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8007) Consolidate logging of binary data

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-8007: -------------------------------------- Summary: Consolidate logging of binary data Key: ISPN-8007 URL: https://issues.jboss.org/browse/ISPN-8007 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Provide more consistent binary data logging for clients and server. The primary method for logging binary data so far was {{{Util.printArray}}} and related methods that printed binary data in straight hex format, e.g. {code} Body value: 0304380000001 {code} In ISPN-7517, Dan added a new way of representing binary data with the added benefit that ascii data is represented as ascii, making it easier to debug things like cache names, e.g. {code} Decode buffer (32768)...\R\Y\_\A\S\P\_\A\D\M\I\N\>17\S\e\t\ \G\o\o\g\l\e\-\A\n\y\l\y\t\i {code} This latter method can be easier to deal with compared with previous method. We should convert all code to the same logging mechanisms so that it's easier to trace things. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5073) Improve "Number of Entries" stats

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5073?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-5073: ------------------------------------------- Moving to Won't fix. If this is an issue we can reopen it. > Improve "Number of Entries" stats > --------------------------------- > > Key: ISPN-5073 > URL: https://issues.jboss.org/browse/ISPN-5073 > Project: Infinispan > Issue Type: Task > Components: Core, JMX, reporting and management > Affects Versions: 7.1.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > > Currently the getNumberOfEntries in CacheMgmtInterceptor returns the size of the datacontainer which doesn't take into account expired entries and cache stores. > To avoid compatibility issues, modify the description to reflect its behaviour and add proper statistics, possibly with different flag combinations (SKIP_REMOTE, SKIP_CACHE_LOAD) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5073) Improve "Number of Entries" stats

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-5073?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic resolved ISPN-5073. --------------------------------------- Resolution: Won't Fix > Improve "Number of Entries" stats > --------------------------------- > > Key: ISPN-5073 > URL: https://issues.jboss.org/browse/ISPN-5073 > Project: Infinispan > Issue Type: Task > Components: Core, JMX, reporting and management > Affects Versions: 7.1.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Fix For: 9.1.0.Final > > > Currently the getNumberOfEntries in CacheMgmtInterceptor returns the size of the datacontainer which doesn't take into account expired entries and cache stores. > To avoid compatibility issues, modify the description to reflect its behaviour and add proper statistics, possibly with different flag combinations (SKIP_REMOTE, SKIP_CACHE_LOAD) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6393) Add ability to hide configuration properties

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6393?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-6393: ------------------------------------------- Won't fix. In practice, we deal with this issue by simply making a different HTML for the specific build if such a need arises. > Add ability to hide configuration properties > -------------------------------------------- > > Key: ISPN-6393 > URL: https://issues.jboss.org/browse/ISPN-6393 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 8.2.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Minor > > We should add ability to hide certain configuration fields if needed. We could hide these fields directly from javascript or preferably from some specific configuration file. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017