• Bug
  • Status: Closed
  • 1 Critical
  • Resolution: Fixed
  • ehcache-core
  • hsingh
  • Reporter: hsingh
  • February 10, 2010
  • 0
  • Watchers: 0
  • January 17, 2013
  • April 30, 2010


  • hsingh (3.00 k) application/x-zip-compressed test.zip


Attached code, creates a cacheManager programattically. it doesnt contain any ehcache.xml, so no default cacheMgr available.

Run using mvn clean install tc:dev-console tc:run

Ehcache Panel shows No Active CacheManager found.


Fiona OShea 2010-02-16

What do you want to do with this??

Gary Keim 2010-02-23

This is a real bug in ehache-core. When the CacheManager is created it consults the passed-in configuration for any Terracotta-clustered caches and, if found, creates the terracottaClusteredInstanceFactory. If your config doesn’t include a Terracotta-enabled cache configuration or the default configuration doesn’t specify Terracotta clustered, then when you go to manually add a TC-enabled cache, the terracottaClusteredInstanceFactory is not set and the cache will not be clustered.

See the init and addCache methods of CacheManager.

This is for Transparency.

Fiona OShea 2010-02-23

Workaround: Make default configuration include Terracotta clustered

Fiona OShea 2010-02-23

document the workaround for 3.2.1/Darwin Fix for Esperance

Fiona OShea 2010-03-05

Added Release note http://www.terracotta.org/confluence/display/docs/Release+Notes

Himadri Singh 2010-05-10

Verified by running cachetest which creates cache programatically. Dev-console shows the cache in ehcache-panel.