Is TreeeCacheAOP thread-safe

[loopingrage]

I have an existing IVR/J2EE application that uses a stateful EJB for maintaining call state. Is it feasable to use one instance of TreeCacheAOP per-VM (ala singleton) or should I create a TreeCache/startService() per call.

Are there any contention/locking issues I should be aware of when using a single instance? or is the CacheManager keeping a queue of requests or something similar?

[ben.wang]

1. You should have just one instance of TreeCacheAop per-VM in general.

2. Be sure to use transaction to make sure the concurrent access.

-Ben