Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 904139

Summary: JON jdg server plugin - Operations on caches / managers are disabled / unavailable = grey color, not clickable in GUI.
Product: [JBoss] JBoss Data Grid 6 Reporter: Tomas Sykora <tsykora>
Component: JON PluginAssignee: William Burns <wburns>
Status: CLOSED NOTABUG QA Contact: Martin Gencur <mgencur>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: gsheldon, jdg-bugs, mhusnain, mmarkus, myarboro
Target Milestone: ---   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
The Infinispan subsystem of JBoss Data Grid Server only exposes metrics and statistics to the JBoss Operations Network plug-in. It does not yet expose the operations which are possible on a cache's components. Therefore, it is not possible to invoke operations on cache containers and caches via the JBoss Operations Network JBoss Data Grid Server plug-in. </para> <para> There is currently no way to invoke the missing operations via the JBoss Operations Network JBoss Data Grid Server plug-in. However some of these operations can be invoked by connecting to the JBoss Data Grid server via JMX or via the JBoss Data Grid CLI.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-10 09:46:48 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:
Bug Depends On:    
Bug Blocks: 1017190    
Attachments:
Description Flags
2 ispn subsystems in DR1
none
DR2 - Grey operations (only 1 subsystem now) none

Description Tomas Sykora 2013-01-25 14:42:56 UTC 
I don't know whether this is known or not (expected or not implemented yet). 

After fix of ResourceBundles issue I was able to reach caches in JON and wanted to issue some operations. (take into the note that I can see statictics normally now)

However, operations label on right-click menu is grey, not clickable at all.
Comment 2 Tomas Sykora 2013-02-27 13:27:22 UTC 
Nice, cache operations are available in ER12 client-server plugin so we can issue these operations directly from JON. 

Any problems / new feature requests (add operations etc.) will be discussed in *other/new* BZs. This BZ was ONLY for doing this possible.

Thanks Tristan.
Setting as VERIFIED
Comment 4 Tomas Sykora 2013-08-12 08:31:49 UTC 
Reopening this bug to not make a mess in BZ.

Using JON 3.1.2.GA as usual and new rhq-jboss-as-7-plugin-4.6.0.JON.jar plugin for AS.

Changes since 6.1.GA -- we have to name folder of JDG server including "as" string. Instead of edg0 it has to be edg-as-0. "as" like ap. server. This mechanism should be better in the future according to JON dev guys.

DR1: we experienced strange behavior of server plugin (in DR1 it was still Infinispan 5.3.x plugin, in DR2 it is JDG Server 6.2.x named plugin). We saw 2 Infinispan subsystem resources. We were able to issue operations on one of them. The second one had operations on caches and cache managers disabled.

Please, see attached picture DR1jon2ispnSubsystemsBug.png.

DR2: (=recent version of reporting bug) There is only one Infinispan subsystem resource detected in JON, but to say it informal: this is the "bad" one. 

Operations on caches and managers are GREY, not reachable and switched off in JON GUI.

For quick details see DR2jon1ispnSubsystemButGreyOpsOnCaches.png.

The difference between DR1 and DR2 server plugin is only RENAMING. So I expect "problems" somewhere on the JDG server level itself.
Comment 5 Tomas Sykora 2013-08-12 08:33:09 UTC 
Created attachment 785608 [details]
2 ispn subsystems in DR1
Comment 6 Tomas Sykora 2013-08-12 08:33:56 UTC 
Created attachment 785609 [details]
DR2 - Grey operations (only 1 subsystem now)
Comment 7 Tomas Sykora 2013-08-28 05:08:46 UTC 
I saw this warning in JON (exclamation mark in yellow triangle for status of JDG server resource)

org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for resource Resource[id=10018, uuid=027c6688-7f8f-4843-a35c-4f8fa9176ada, type={JBossAS7}JBossAS7 Standalone Server, key=/home/hudson/jboss-as-jdg6-node1/standalone, name=AS (0.0.0.0:9990), parent=auto-jdg-agent1.bc.jonqe.lab.eng.bos.redhat.com, version=jdg6-node1].
	at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1776)
	at org.rhq.core.pc.inventory.InventoryManager.refreshResourceComponentState(InventoryManager.java:3039)
	at org.rhq.core.pc.inventory.InventoryManager.mergeResource(InventoryManager.java:2939)
	at org.rhq.core.pc.inventory.InventoryManager.mergeModifiedResources(InventoryManager.java:2806)
	at org.rhq.core.pc.inventory.InventoryManager.synchInventory(InventoryManager.java:1137)
	at org.rhq.core.pc.inventory.InventoryManager.synchInventory(InventoryManager.java:1097)
	at org.rhq.core.pc.inventory.InventoryManager.handleReport(InventoryManager.java:1079)
	at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:126)
	at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:61)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
Caused by: org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: The original product type discovered for this AS7 server was JBoss AS 7, but the server is now reporting its product type is [JBoss JDG 6].
	at org.rhq.modules.plugins.jbossas7.BaseServerComponent.validateServerAttributes(BaseServerComponent.java:182)
	at org.rhq.modules.plugins.jbossas7.BaseServerComponent.getAvailability(BaseServerComponent.java:116)
	at org.rhq.modules.plugins.jbossas7.BaseServerComponent.start(BaseServerComponent.java:92)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	... 3 more


I named jdg server home directory as jboss-as-jdg-node1 to contains "-as-" string there to make JON possible to discovery jdg as a "as" server type. Maybe this causes problems. (But we need some mechanism for recognition)
Comment 8 Tomas Sykora 2013-09-23 09:37:49 UTC 
ER1:

This bug is surpassed by https://bugzilla.redhat.com/show_bug.cgi?id=1006372 ( Jon plugin - duplicate infinispan resource)

Operations are clickable and ok, but only on one of the resources. In fact, the second (duplicate) shouldn't be present at all. 
This is very confusing for automated tests.

This BZ is maybe not relevant now and "the only problem" is duplicition of resources. One provides (clickable gui) operations and the second not.
Comment 9 Tomas Sykora 2013-10-10 09:46:48 UTC 
Closing this one.

Once https://bugzilla.redhat.com/show_bug.cgi?id=1006372 is FIXED, this will no longer be an issue.