Hide Forgot
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
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).
And one more thing...this is a regression that happened sometime during last month, this worked fine with EDG in December.
Does this still happen ?
Yes. Tested with ER2.
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.
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?
Library should work fine. Code change would mean producing separate Infinispan libraries so I'd rather go with "not support". WDYT ?