Bug 919034

Summary: JON server plugin, xsite MBean - status shouldn't probably be operation but metric
Product: [JBoss] JBoss Data Grid 6 Reporter: Tomas Sykora <tsykora>
Component: JON PluginAssignee: William Burns <wburns>
Status: CLOSED WONTFIX QA Contact: Martin Gencur <mgencur>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: myarboro, ttarrant
Target Milestone: CR1   
Target Release: 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
The JBoss Operations Network Server plug-in exposes a non-functional "status" operation on a remote site. Consequently, invoking the operation returns an error. </para> <para> As a workaround, use the CLI "site --status ${SITE}" command instead. </para> <para> As a result of this bug, it is not possible to obtain the status of a remote site using the JBoss Operations Network plug-in however, it is possible when using the CLI.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-16 06:04:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Sykora 2013-03-07 13:10:56 UTC
JON 3.1.2 jdg CR1 server plugin, jdg server started with clustered-xsite.xml to show backup sites properly under default cache.

Operations: Take site offline and Bring site online was issued successfully. Verified via jdg CLI console.

There is the third operation here - Status.
JDG code, LocalDescription.properties says: infinispan.backup.ops.site-status=Displays the current status of the backup site.

When site is taken offline, JON can't register this change properly. *It looks like "Status" should be a metric, not an operation.* After that JON should be able to detect whether site is offline or online.

This metric itself is changing properly in jdg (we can see it in site status via jdg CLI console). 


Issuing operation Status on SFO site, JON says now:

java.lang.Exception: JBAS014739: No handler for status at address [
    ("subsystem" => "infinispan"),
    ("cache-container" => "clustered"),
    ("distributed-cache" => "default"),
    ("backup" => "SFO")
], rolled-back=true
	at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

Comment 1 Misha H. Ali 2013-03-13 04:14:01 UTC
Should this be included in release notes for 6.1? If so, please set the requires_doc_text? flag and add some CCFR information (and a workaround, if one exists).

Comment 2 gsheldon 2013-03-13 23:17:26 UTC
Minor edits to doc_text field for 6.1 Release Notes.

Comment 3 Misha H. Ali 2013-05-07 03:41:18 UTC
Set flag to nominate this bug for 6.2 release notes.

Comment 4 Misha H. Ali 2013-06-18 04:18:07 UTC
This looks like a known issue. changes doc type field to reflect this.

Comment 9 Tomas Sykora 2014-07-22 13:58:36 UTC
We want to fix it for 6.4.0. Making our management solution better this time.

Will I will need to check with latest env. setups and add informations accordingly.