From 9dda0bbeab053cc4a09f7d54176d074179fdf9e4 Mon Sep 17 00:00:00 2001 From: Simon Brandhof Date: Thu, 28 Aug 2014 16:02:35 +0200 Subject: SONAR-4898 try to fix ping monitoring Sometimes child autokills because it did not receive pings in the last 30 seconds. I hope it comes from the parent process that is slow to start monitoring (send pings). --- sonar-application/src/main/java/org/sonar/application/App.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sonar-application/src') diff --git a/sonar-application/src/main/java/org/sonar/application/App.java b/sonar-application/src/main/java/org/sonar/application/App.java index 784d75ef299..23293a2efed 100644 --- a/sonar-application/src/main/java/org/sonar/application/App.java +++ b/sonar-application/src/main/java/org/sonar/application/App.java @@ -70,7 +70,7 @@ public class App implements ProcessMXBean { .addClasspath("./lib/common/*") .addClasspath("./lib/search/*"); if (elasticsearch.execute()) { - monitor.registerProcess(elasticsearch); + monitor.monitor(elasticsearch); if (elasticsearch.waitForReady()) { logger.info("search server is up"); @@ -92,7 +92,7 @@ public class App implements ProcessMXBean { server.addClasspath(driverPath); } if (server.execute()) { - monitor.registerProcess(server); + monitor.monitor(server); if (server.waitForReady()) { success = true; logger.info("web server is up"); -- cgit v1.2.3