Bug 785105

Summary: A cache started over JMX does not appear among caches in the JMX view
Product: [JBoss] JBoss Data Grid 6 Reporter: Martin Gencur <mgencur>
Component: ServerAssignee: Tristan Tarrant <ttarrant>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: jawilson, jdg-bugs, myarboro
Target Milestone: ---   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-29 12:03:38 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:
Attachments:
Description Flags
JConsole screenshot of the problem none

Description Martin Gencur 2012-01-27 10:02:38 UTC
Description of problem:

When starting a cache via startCache JMX operation on a CacheManager MBean, the cache is really started but does not show among the caches in the JMX view. I'll attach a screenshot. 

This is most likely a problem of Infinispan subsystem in EDG/AS because I also tried this with standalone Infinispan server (community one) 5.1.0.FINAL and it worked fine there.


Version-Release number of selected component (if applicable):

Tested version of EDG specified here: https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-edg-from-source/101/artifact/versions.txt

Comment 1 Martin Gencur 2012-01-27 10:05:20 UTC
Created attachment 557835 [details]
JConsole screenshot of the problem

The attached image shows that there are only 2 caches in the view while there are more caches running (I started a few caches over JMX and they did not appear in the view).

Comment 2 Martin Gencur 2012-01-27 10:09:52 UTC
And one more thing...this is a regression that happened sometime during last month, this worked fine with EDG in December.

Comment 3 Tristan Tarrant 2012-03-08 13:00:40 UTC
Does this still happen ?

Comment 4 Tristan Tarrant 2012-03-08 13:02:16 UTC
Does this still happen ?

Comment 5 Martin Gencur 2012-03-08 14:53:47 UTC
Yes. Tested with ER2.

Comment 6 Tristan Tarrant 2012-03-09 08:30:00 UTC
I think we should disallow starting/stopping caches via JMX in server mode, as this is handled directly by Infinispan and not by the Infinispan subsystem. The Infinispan subsystem associates a service for each container and cache, and starting/stopping the cache via JMX will not start/stop the corresponding service.

Comment 7 Jimmy Wilson 2012-03-15 17:33:09 UTC
I think I agree with Tristan's comments above in that server mode users shouldn't be doing this.  What about library mode, however?

Tristan, can you elaborate on what disallow means?  Do you mean "not support" as in support policy or "prevent" as in a code change?

Comment 8 Tristan Tarrant 2012-03-16 16:12:11 UTC
Library should work fine. Code change would mean producing separate Infinispan libraries so I'd rather go with "not support". WDYT ?