[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6776:
------------------------------
Attachment: domain.xml
host.xml
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: domain.xml, host.xml
>
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6776:
------------------------------
Attachment: (was: host.xml)
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-6776) Administration console - push state transfer and cancel state transfer buttons don't work properly
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6776?page=com.atlassian.jira.plugin.... ]
Roman Macor updated ISPN-6776:
------------------------------
Attachment: (was: domain.xml)
> Administration console - push state transfer and cancel state transfer buttons don't work properly
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-6776
> URL: https://issues.jboss.org/browse/ISPN-6776
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
>
> Click on cache container -> Actions -> Manage backup sites -> Push state (on BRN site which is configured)
> result: nothing happens, server log:
> [Server:server-one] 15:15:03,752 ERROR [org.jgroups.protocols.relay.RELAY2] (ServerService Thread Pool -- 36) master:server-one: no route to BRN: dropping message
> expected result: Success! The operation has been successfully executed.
> Please note that if we take the site offline and then online again in the "Manage backup sites" dialog, push state button works correctly.
> Cancel state button is behaving the same, except taking site offline and then online again doesn't help.
> I'm attaching server configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-6742) Console shows cache available and disabled at the same time
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6742?page=com.atlassian.jira.plugin.... ]
Roman Macor commented on ISPN-6742:
-----------------------------------
[~vblagojevic] the discussion makes sense, but I think that the disabled status should be reflected somehow in cache container.
Right now cache, in cache list shows OK status (green tick icon) if the cache is available and the only way to see that it's disabled is by clicking on it.
I suggest that cache would have OK status only if it's available and enabled, what do you think?
> Console shows cache available and disabled at the same time
> -----------------------------------------------------------
>
> Key: ISPN-6742
> URL: https://issues.jboss.org/browse/ISPN-6742
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 8.2.2.Final
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Alpha3
>
> Attachments: attachment.png
>
>
> Page: go to cache detail and click "Actions" -> "Disable".
> After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-7236) Administration console - management of remote sites is not working
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7236?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-7236:
-------------------------------------------
No, [~rmacor] it was not. Likely a regression from our implementation of standalone mode. Will keep you updated!
> Administration console - management of remote sites is not working
> ------------------------------------------------------------------
>
> Key: ISPN-7236
> URL: https://issues.jboss.org/browse/ISPN-7236
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 9.0.0.Alpha4
> Reporter: Roman Macor
> Assignee: Vladimir Blagojevic
> Attachments: domain.xml, host.xml
>
>
> Start the server with the attached configuration.
> Click on cache container -> MemcachedCache has a correct icon "Remotely backed up", but there should also be the name of the back up site - BRN in this case.
> [~vblagojevic] was this removed on purpuse?
> *click actions -> Manage back up sites -> clicking on any actions results in:*
> Error There has been an error executing the operation: WFLYCTL0031: No operation named 'BRN' exists at address [ ("subsystem" => "datagrid-infinispan"), ("cache-container" => "clustered") ]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-6672) Incorrect cache contents entries count
by Roman Macor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6672?page=com.atlassian.jira.plugin.... ]
Roman Macor resolved ISPN-6672.
-------------------------------
Fix Version/s: 9.0.0.Alpha4
Resolution: Done
I can confirm, this is no longer an issue.
> Incorrect cache contents entries count
> --------------------------------------
>
> Key: ISPN-6672
> URL: https://issues.jboss.org/browse/ISPN-6672
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Alpha2, 8.2.2.Final
> Reporter: Galder Zamarreño
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.0.Alpha4
>
> Attachments: Incorrect cache content entries displayed.png
>
>
> "Cache Contents / Entries" field in management not correctly calculated. The screenshot should show 101 entries and not 50. See steps to reproduce.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-7235) Cross site replication fails if authentication is enabled
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7235?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7235:
----------------------------------
Status: Open (was: New)
> Cross site replication fails if authentication is enabled
> ---------------------------------------------------------
>
> Key: ISPN-7235
> URL: https://issues.jboss.org/browse/ISPN-7235
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication, Security
> Affects Versions: 9.0.0.Alpha4, 8.2.5.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.0.0.Beta1, 8.2.6.Final
>
>
> org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-2,shared=tcp-global) ISPN000071: Caught exception when handling command SingleXSiteRpcCommand{command=ClearCommand{flags=null}}: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN' permission
> at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76)
> at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:44)
> at org.infinispan.security.impl.SecureCacheImpl.getCacheConfiguration(SecureCacheImpl.java:454)
> at org.infinispan.xsite.BackupReceiverRepositoryImpl.createBackupReceiver(BackupReceiverRepositoryImpl.java:163)
> at org.infinispan.xsite.BackupReceiverRepositoryImpl.getBackupReceiver(BackupReceiverRepositoryImpl.java:95)
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommandFromRemoteSite(CommandAwareRpcDispatcher.java:283)
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:252)
> at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:460) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:377) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:250) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:675) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.JChannel.up(JChannel.java:739) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1029) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.deliver(RELAY2.java:618) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.route(RELAY2.java:514) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.handleMessage(RELAY2.java:489) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.handleRelayMessage(RELAY2.java:470) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.Relayer$Bridge.receive(Relayer.java:265) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.JChannel.up(JChannel.java:769) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1033) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:182) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:447) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.stack.Protocol.up(Protocol.java:420) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.deliverBatch(UNICAST3.java:1087) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.removeAndDeliver(UNICAST3.java:886) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:790) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:652) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:200) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:299) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.MERGE3.up(MERGE3.java:286) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.Discovery.up(Discovery.java:291) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2842) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1577) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.TP$MyHandler.run(TP.java:1796) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_101]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_101]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101]
> ~~~
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ISPN-7235) Cross site replication fails if authentication is enabled
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-7235?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-7235:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/4684, https://github.com/infinispan/infinispan/pull/4683
> Cross site replication fails if authentication is enabled
> ---------------------------------------------------------
>
> Key: ISPN-7235
> URL: https://issues.jboss.org/browse/ISPN-7235
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication, Security
> Affects Versions: 9.0.0.Alpha4, 8.2.5.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 9.0.0.Beta1, 8.2.6.Final
>
>
> org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (Incoming-2,shared=tcp-global) ISPN000071: Caught exception when handling command SingleXSiteRpcCommand{command=ClearCommand{flags=null}}: java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN' permission
> at org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:76)
> at org.infinispan.security.impl.AuthorizationManagerImpl.checkPermission(AuthorizationManagerImpl.java:44)
> at org.infinispan.security.impl.SecureCacheImpl.getCacheConfiguration(SecureCacheImpl.java:454)
> at org.infinispan.xsite.BackupReceiverRepositoryImpl.createBackupReceiver(BackupReceiverRepositoryImpl.java:163)
> at org.infinispan.xsite.BackupReceiverRepositoryImpl.getBackupReceiver(BackupReceiverRepositoryImpl.java:95)
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommandFromRemoteSite(CommandAwareRpcDispatcher.java:283)
> at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:252)
> at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:460) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:377) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:250) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:675) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.JChannel.up(JChannel.java:739) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1029) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.deliver(RELAY2.java:618) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.route(RELAY2.java:514) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.handleMessage(RELAY2.java:489) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.RELAY2.handleRelayMessage(RELAY2.java:470) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.relay.Relayer$Bridge.receive(Relayer.java:265) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.JChannel.up(JChannel.java:769) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1033) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:182) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:447) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.stack.Protocol.up(Protocol.java:420) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.deliverBatch(UNICAST3.java:1087) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.removeAndDeliver(UNICAST3.java:886) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:790) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:652) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:200) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:299) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.MERGE3.up(MERGE3.java:286) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.Discovery.up(Discovery.java:291) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2842) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1577) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at org.jgroups.protocols.TP$MyHandler.run(TP.java:1796) [jgroups-3.6.3.Final-redhat-6.jar:3.6.3.Final-redhat-6]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_101]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_101]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_101]
> ~~~
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months