• Bug
  • Status: Closed
  • 0 Showstopper
  • Resolution: Fixed
  • ehcache,ehcache-monitor,ehcache-probe
  • hsingh
  • Reporter: amiller
  • November 05, 2009
  • 0
  • Watchers: 0
  • January 17, 2013
  • November 06, 2009


Currently, if you start the ehcache probe, then start the ehcache monitor server, the probe does not re-register itself with the monitor server and will not show up. If the probe cannot connect with its designated master, it should periodically re-try the connection. Might need some properties around that, not sure.


Geert Bevin 2009-11-05

Actually, the retry logic is in there now, I thought you were talking about something else when we talked on IM. You can start a probe and it will retry 10 times while waiting 30 secs in between, there can be set through properties. Is something else needed?

Alex Miller 2009-11-05

Hmm, that’s not what I saw but maybe I didn’t wait long enough. I think it should try for longer than that (maybe even forever) though but we can see what PM thinks.

Geert Bevin 2009-11-06

It should output to the logs that it’s retrying … the actual behavior is tweakable of course, waiting for PM for this then?

Steve Harris 2009-11-06

I think it should retry for ever.

Geert Bevin 2009-11-06

Retrying forever now

Himadri Singh 2009-11-16

Covered in ehcache-dx lrt. Probes registers to monitor even after 10 mins. Following loggins keeps on printing each 30 secs.

Nov 16, 2009 2:16:41 AM org.terracotta.ehcachedx.monitor.util.RestProxy registerProbe WARNING: Error connecting to the server at address ‘localhost’ and port ‘9999’, retrying in 30 seconds …