[JBoss JIRA] (ISPN-7955) Hot Rod client needs to re-resolve topology addresses after failure to connect
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-7955?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-7955:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.1.0.Final
Resolution: Done
> Hot Rod client needs to re-resolve topology addresses after failure to connect
> ------------------------------------------------------------------------------
>
> Key: ISPN-7955
> URL: https://issues.jboss.org/browse/ISPN-7955
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 8.2.6.Final, 8.1.7.Final, 9.1.0.Beta1, 9.0.3.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.1.0.Final
>
>
> The Hot Rod client resolves topology addresses on reception. In dynamic environments where server nodes can restart with different IPs (but maintaining their external hostname) this causes the client to fail to reconnect. The client should hold on to the original address and re-resolve it in case of failures.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (ISPN-5073) Improve "Number of Entries" stats
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5073?page=com.atlassian.jira.plugin.... ]
Pedro Zapata closed ISPN-5073.
------------------------------
Resolution: Done
> 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)
7 years, 6 months
[JBoss JIRA] (ISPN-5073) Improve "Number of Entries" stats
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5073?page=com.atlassian.jira.plugin.... ]
Pedro Zapata reopened ISPN-5073:
--------------------------------
> 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)
7 years, 6 months
[JBoss JIRA] (ISPN-5829) Configuration view for node
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-5829?page=com.atlassian.jira.plugin.... ]
Pedro Zapata closed ISPN-5829.
------------------------------
Resolution: Done
> Configuration view for node
> ---------------------------
>
> Key: ISPN-5829
> URL: https://issues.jboss.org/browse/ISPN-5829
> Project: Infinispan
> Issue Type: Sub-task
> Components: Console
> Reporter: Pedro Zapata
> Assignee: Vladimir Blagojevic
> Labels: jdg7
>
> As an administrator, I want to configure a node, review and revise as necessary the transport/discovery protocols, server hinting values.
> The only properties that will be configurable are:
> - Host to run (know which hosts are empty and which ones have server running).
> - JVM configuration.
> - Port offset
> - Server hinting properties.
> - Remote endpoint external address / point - optional
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[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 closed ISPN-7276.
------------------------------
Resolution: Done
> 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
>
> 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)
7 years, 6 months
[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 reopened ISPN-7276:
--------------------------------
> 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
>
> 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)
7 years, 6 months