[JBoss JIRA] (ISPN-7699) Upgrde to protostream-4.0.0.Final
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-7699:
-----------------------------------
Summary: Upgrde to protostream-4.0.0.Final
Key: ISPN-7699
URL: https://issues.jboss.org/browse/ISPN-7699
Project: Infinispan
Issue Type: Component Upgrade
Components: Remote Querying
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Infinispan 9.0.0.Final uses protostream-4.0.0.CR3 which is identical to 4.0.0.Final, so this upgrade is safe both for infinispan 9.1.x and 9.0.1.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months
[JBoss JIRA] (ISPN-7698) Administration console - minor issues with removing node
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7698?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7698:
-------------------------------------------
I noticed this as well as I was making videos about the console. It must have been some sort of a regression on the server side as this information (server group) used to be available for the stopped node. Will issue a fix now
> Administration console - minor issues with removing node
> --------------------------------------------------------
>
> Key: ISPN-7698
> URL: https://issues.jboss.org/browse/ISPN-7698
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Final
> Reporter: Roman Macor
> Priority: Minor
>
> Removing node opens confirmation dialog which says:
> Remove server new-node from undefined?
> Suggested fix:
> The node must be in stopped state to perform the operation so the cluster info is not available. The confirmation might just say: Remove server new-node?
> After clicking confirm the Loading icon is displayed until users click on one of the tabs. (The node is successfully removed)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 9 months