Bug 919034 - JON server plugin, xsite MBean - status shouldn't probably be operation but metric
Summary: JON server plugin, xsite MBean - status shouldn't probably be operation but m...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: JON Plugin
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR1
: 6.4.0
Assignee: William Burns
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-07 13:10 UTC by Tomas Sykora
Modified: 2020-09-16 06:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-16 06:04:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.