Hi, 2008/12/15 Ian Boston <[email protected]>: > The default caching mechanism is ehcache, which has a JMX interface, and I > think its enabled.
Yes it is, see shindig.cache.ehcache.jmx.enabled in the shindig.properties It is why I was thinking that jmx could be used. > I am not certain if it has exposed functions to clear various caches, but if > enabled it will have statistics. > > This is a level lower than the gadget server which may have other cache > flush mechanisms more specific to gadgets, I notice Kevin as responded > later. > > FYI, try running tomcat or jetty with -Dcom.sun.management.jmxremote and > then connecting to the running tomcat with jconsole Basically, MAVEN_OPTS=-Dcom.sun.management.jmxremote mvn -Prun jconsole See [1] for more information. Cheers, Vincent [1] http://docs.codehaus.org/display/JETTY/Running+Jetty+with+jconsole > If you look for the MBean tab you should see some ehcache beans somewhere in > the tree. > > If you don't, shout, and we can enable JMX on ehcache. > Ian > > On 16 Dec 2008, at 05:31, Vincent Siveton wrote: > >> Hi Arnaud, >> >> Le 15 décembre 2008 08:59, <[email protected]> a écrit : >>> >>> Hello, >>> I am new to shindig (and opensocial development in general). We are >>> developing on our project various gadgets and features, and we are >>> running on issues with caching on development environment. We need to >>> restart the server in order for modifications on the gadgets XML or >>> features descriptors to take effect. >>> >>> Is there a way to tell shindig server (java version) to reload >>> everything, orflush cache or whatever ? I must confess I do not have a >>> clear understanding of the archietecture of the whole thing. >> >> I guess surely via jmx. >> >> Cheers, >> >> Vincent > >
