Terracotta Discussion Forums

Can you try with the SingletonEhcacheProvider instead?

I strongly suspect a bug here. Could you help us raise a comminity JIRA to track an fix this. The more details provided in the JIRA, the better it is for us to help reproduce this. If you have a sample app that reproduces this, that would be very helpful as well.

Its probably hibernate related. Can you share your Ehcache version, hibernate version and TSA version.
I suspect it to be innocuous but doesnt hurt creating a community JIRA ticket for our eng team to investigate.

Search is enterprise only feature.

I re-read your post a few times. Seems like you are looking for an API that records an expiration (either due to time, count or size or custom eviction including removeAll, remove, events etc) and generates a certain statistic on this based on the number of hits that element contains. The API doesnt have this as of today - I suspect its probably because its an expensive calculation though I could be wrong on that.
Anyways, in the absence of that, perhaps, you could calculate this manually through some custom decorators/listeners. (might get expensive as well depending on the size of dataset and how you are calculating this)

We are coming up with a document that helps with this migration strategy for DSO users moving to Express mode. Stay tuned. Unfortunately, this migration cannot be automated.
Just to add, moving to Express will remove any custom instrumentation that you might have, standardize the deployment using Ehcache API or JSR107 or any other persistance fwks like hibernate, plus give you options for performance and scale. We will be glad to walk you through any other concerns - just give us a shout out sales@terracottatech.com.

Firstly I would like to thank you for being a proponent of Terracotta over the past 6 years. We appreciate that and hope you continue to spread the good word.
Not sure when you last took a look at the Express product but it now handles a lot of the custom features that you are looking for. A lot of it has been back-ported from the DSO world and simplified as well. In addition it offers a comprehensive scale and performance options.
With regard to DSO go ahead approach, someone from our team will reach out to you directly and keep you apprised of the go forward approach.

Doesnt this help

http://ehcache.org/documentation/apis/explicitlocking

If you have more licensing questions, just shoot an email to sales@terracottatech.com

You are correct. There is no expiration.

Nice ;) Thanks for sharing this.

Looks good to me. Try to use the singleton factory instead. Whats your ehcache version and your hibernate version?

A few questions

1. Whats your quartz version?
2. I am not sure I completely understand what you mean by "thread is hung" and "hung instance" - can you be more specific here?

I am not sure if this helps but if you do not want the same job to run concurrently, you might want to add the @DisallowConcurrentExecution annotation.

A few things. Based on my experience with using hibernate, if you want additional control, you need to use caching outside of second level cache, you can use Ehcache itself. I call it using POEO - plain old ehcache objects.
Now, if you use ehcache directly, you could decorate your original cache and populate a secondary cache (with eternal=true) with your results. While you will be storing the results twice, you can use the second cache when the service calls fails and null. The second cache is eternal and will never lose its contents.

Anyways, this is just one of the design patterns that I can think of. I am sure you can get fancy.

We had some maintenance going on. It should be accessible now