Terracotta Discussion Forums

We can only help if you provide some details about what you've done. Please show your quartz.properties files.

I am using echcache web with spring. In my simple CachingFilter, the getCacheManager define as following:

protected net.sf.ehcache.CacheManager getCacheManager() {

return CacheManager.getInstance();
}

It works fine, but only problem is that, I do not know how to get reference of that CacheManager. If it is avaialbe, I would be able to manage elements in cache programmatically.

Any one know how to do it?

We must be having a language problem because what is quoted above doesn't make sense. Maybe try restating what you mean by "I do not know how to get reference of that CacheManager" because that method gives you the reference.

Another thing you can do is to show more of the details of your app/config so we can have more context.

Did you do what stylex7 recommended above?

You've provided a view of JConsole on the QuartzManager application. I was looking for the attributes of your Quartz-enabled application. It would look something like the attached.

Did you enable statistics in your config?

<cache statistics="true"/>

There's a situation where the DevConsole won't see your caches. You don't have your defaultCache configured as terracottaClustered and you don't have any terracottaClustered caches. Basically the DevConsole will only see your caches if you have at least one terracottaClustered cache or your defaultCache is terracottaClustered.

https://jira.terracotta.org/jira/browse/DEV-5937

A problem with the Big Buttons not being enabled appropriately was fixed in the 3.5 line. If you are using 3.5, please check ~/.devconsole.log for any uncaught exceptions that may be the cause.

http://community.jboss.org/message/71381

See here: http://forums.terracotta.org/forums/posts/list/4886.page

Either the CacheManager has been shutdown or the cache has been removed from the CacheManager. The DiskStore has been disposed and the thread pool shutdown.

Also, you should really add the Cache to a CacheManager or you'll be missing out on some features.

Give it another try.

I'm seeing a similar error using our upcoming 3.5.2 release. Will check it out.

The QuartzScheduler has an API for managing jobs. Start learning about it here: http://www.quartz-scheduler.org/docs/

You will need to provide more details, such as what version of Quartz you are using, the code for your job, and the OAS log file.