[Logo] Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Messages posted by: ljacomet  XML
Profile for ljacomet -> Messages posted by ljacomet [77] Go to Page: Previous  1, 2, 3, 4, 5, 6 Next 
Author Message
Hello Amber,

In order to do this change, you have two solutions:
* Stop the cluster and delete all files - this will erase all data for all caches and allow you to start again with different configuration values.
* Pick a different cache name

What you are seeing here is the consequence of the distributed cache having been created with initial settings of 100 for TTI and TTL.
Once set, these values cannot be changed.
When you disconnect your client, the distributed cache remains, and so when trying to connect from your client with the same cache name but with different settings you hit this exception that indicates a configuration mismatch.

The storage model has evolved over the different product versions.

The 4.0.x model is a pyramidal one, where an entry is always present in the lower cache layer, disk in your case.
It means that an entry, when put in the cache, will always be written to disk.

This also means that the total configured cache size is determined by the size of the lower layer, 200M in your case.
Objects are serialized to disk in order for the cache to be restartable.
This means that when you do changes on the returned entry from the cache, these changes are not propagated to the serialized entry.
You need to put this modified object into the cache for the changes to survive a restart.
The exception you have is because you are using

If you are using non serializable objects, you should use

And similar methods exist for the key.

As you found in the documentation, this limits the cache storage option to on-heap only.
Hi Erez,

No there is no way to do that with a Cron expression.
From CronExpression javadoc:

Thus "7/6" in the month field only turns on month "7", it does NOT mean every 6th month, please note that subtlety.


Have a look at the tutorial lesson 6 and its cron documentation.

Specifying 1/3 means every three month starting at month one and is equivalent to:
So not triggering in June is expected, but I admit triggering in August looks wrong too.

You should be able to find information on this topic there:
Are you sure both tomcat instances have access to your class com.test.rewards.domain.RewardEvent?
All artifacts are now available in Terracotta public repository, so you should be able to build from source.
Hi Jeroen,

A number of released artifacts did not make it yet in the public Terracotta repository. This should be resolved in the coming days.

If you need a solution right now, you can:
- Add back the -SNAPSHOT version on artifacts that are not resolved (statistics version 1.0.1-SNAPSHOT)
- Move to the next SNAPSHOT version by incrementing the released version number by one and adding SNAPSHOT to it. (statistics version 1.0.2-SNAPSHOT)
I am indicating both options as some of these snapshots may also not be available.

This should give you a valid setup until all artifacts are properly published.

I will update this post once it happens.
Could you indicate the version of Ehcache you are using?

Could you also share more of the stack traces? Why do you think the deadlock is inside Ehcache?

It is hard to conclude anything from the extracts shared here.
This looks like a Spring issue or a Tomcat class scanning one.

You may want to have a look at SPR-8275

Hope this helps.
Your application does not find any ehcache configuration file in its classpath.

Have a look at the documentation on ehcache-failsafe.xml

And then you have an exception.

Hard to say anything more as you provide very little information.
Your issue is a classpath or spring one, nothing specific to quartz.

You would get better support on the Spring forums
Profile for ljacomet -> Messages posted by ljacomet [77] Go to Page: Previous  1, 2, 3, 4, 5, 6 Next 
Go to:   
Powered by JForum 2.1.7 © JForum Team