Terracotta Discussion Forums

Our environment: Terracotta 3.5.2 in networked active-passive mode (2 nodes total); 2 clustered clients (Spring/Hibernate running in Tomcat 6).

Our issue: clients are able to connect to the Terracotta cluster, but the Dev Console is inconsistently representing the connected clients, which limits our ability to investigate issues.

For example, in the main navigational hierarchy, under Terracotta cluster -> Topology -> Connected Clients, no clients are displayed. However, if I go to Monitoring -> Runtime Statistics, the two clients appear in the Select View dropdown.

The terracotta server is showing traffic, so the clients are actually connected and utilizing the L2 cache.

Any ideas what's going on?

Addendum: since the left-hand nav thinks there are no connected clients, it also is hiding the Ehcache and Hibernate monitoring tools.

Also note that this is an existing production install; it all worked fine until a few weeks ago. There's been no changes to the Terracotta config in that period.

dpb,

This is a known issue with Dev Console with the version of Terracotta you are using. In a lot of cases, it helps if you disconnect and reconnect again?
If that doesn't help, can you upgrade to the latest version of TC? This has a few fixes that might help you.

Plus going forward, there will be new SOAP and restful API to get access to the same data - stay tuned for updates. Current version is for standalone and is available here http://ehcache.org/documentation/beta/