Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Here you go:-

http://terracotta.org/documentation/bigmemorymax

If you need more details or need any help on any topics, Please let us know.

If you are using stand alone EhCache, then by using Java runtime parameters i.e:- XMS and XMX you can increase the heap size of your application and then using ehcache xml you can configure the size of your caches as well.

Please follow this link for more details:-
http://ehcache.org/documentation/configuration/cache-size

If you are using distributed EhCache, please revert we can help you in that as well.

@junaidjp:- I assume that you are using cache.getSize() method after the expiration time period to calculate the cache size. But if you try to access a expired element, null will be returned.

Elements in memory are expired on access, while elements on disk are expired by a thread that runs in background.

Hi,
Can you please share your config files here.

Please go through the following links, just in case you have not missed anything:-
http://ehcache.org/documentation/user-guide/hibernate

http://terracotta.org/documentation/enterprise-ehcache/get-started-hibernate

Going by the trace:-
"WARNING: packet from 192.168.2.27:45566 has different version (2.10.0) from ours (2.6.2). This may cause problems"

Can you please make sure 192.168.2.27 also has the same version of JGroups, which in your case is 2.10.0

Can you please post the full stack trace, or probably full logs will better. We will have to look where this null pointer exception is coming from.

Puneet Chandila (Terracotta Field Engineer)

Hi Chrismas,

There are too many factors on which the response time of the method isKeyInCache will depend. In general it is quite a fast method.

So it would be great if you can provide us the details about your usecase and environment, specifically information like hardware setup, L1 & L2 heap size, network speed, total size of the cache, no. of elements in cache, etc.

By providing us this information, we can help you in identifying the probable reason for slow response method, that you are observing.

Thanks,
Puneet

Hi hervbarr,

If I understand your question correctly, your global cache is updated by some other application and you want to pass these modification to other copies of your cache.

I think you can look for Cache Event Listeners in your scenario, you can handle the events like put,get and many other events. So whenever your global cache is updated, you can handle the event as required.

You can follow these link for more details:-
http://ehcache.org/documentation/apis/cache-event-listeners
http://ehcache.org/apidocs/net/sf/ehcache/event/CacheEventListener.html

Thanks,
Puneet

You can follow this link for more details on Distributed Ehcache:-

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

Hi gemsbond,

Can you please describe more about your usecase.

Moreover I would advise you to look into our open source distributed ehcache product, if your requirement is just to distributed cache then you might get a better performance by using distributed ehcache then doing replication.

Just as suggestion, we have have seen certain cases in the past with replication using Jgroup UDP multicast having issues. If possible you can try the RMI replication which also works very well.

Thanks,
Puneet

Hi rivendel,

It would be great if you can post the full error stack trace, which you are getting by using the properties.

It is highly recommended that you try the terracotta express mode which uses ehcache, so that you can get the maximum performance out of your application.

Thanks