Terracotta Discussion Forums

We would suggest you to go for terracotta distributed caching which is much more efficient and easy to use , here's the link for more details :

http://ehcache.org/documentation/get-started/about-distributed-cache

Please don't spam forums.

Latest is ehcache 2.7 .

Can you try this out with latest quartz 2.1.7.

It seems issue is resolved.

Good to know it resolved the issue.

This query is more on database side and not for quartz.

We would suggest you to first go through the complete basics of quartz , here's the link which has useful tutorial, samples which can be helpful :

http://quartz-scheduler.org/documentation/quartz-2.1.x/quick-start

Hmm yes it can be .

Do you have the "tim-tomcat-6.0" installed . You can get the list of tim's using $ tim-get.sh list and then do

$ tim-get.sh install tim-tomcat-6.0 2.1.3 to install the tim for tomcat.

Yes it will be running and you can use retry feature . These properties are here :

retryAttempts - The number of times to attempt writing from the queue. Defaults to 1.
retryAttemptDelaySeconds - The number of seconds to wait before retrying.

Here's the details on write behind which could be helpful :

http://ehcache.org/documentation/apis/write-through-caching#potential-benefits-of-write-behind

Yes it will be running and you can use retry feature . These properties are here :

retryAttempts - The number of times to attempt writing from the queue. Defaults to 1.
retryAttemptDelaySeconds - The number of seconds to wait before retrying.

Here's the details on write behind which could be helpful :

http://ehcache.org/documentation/apis/write-through-caching#potential-benefits-of-write-behind

Good to know that issue is resolved.

I think ehcache is the best option for this.

It is hard to say anything on this with this info, do u have a reproducible use case for this .