Endless Tomcat processes starting and stopping for Synchrony, using ALL CPU

[Al Johnson]

I'm developing plugins and have my own local Confluence Server v6.6.3 running, but maybe this is still relevant to non-developers...

I started Confluence with atlas-debug as usual and there are two Java Tomcat processes constantly starting and stopping and is using ALL of my CPU on all cores.  There are 2 Tomcat Java processes that startup and then get killed about 30 seconds later and then restarting.  Running on Windows 7.

There are only INFO level logs during each time it starts:

[INFO] [talledLocalContainer] 2018-04-25 13:50:54,017 INFO [362:StdOutHandler [C:\Program Files\Java\jdk1.8.0_121\jre\bin\java.exe]] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] startup Starting Synchrony and enabling Collaborative Editing
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,386 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled proxy port present: false
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,386 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled app config synchrony.proxy.enabled: true
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,565 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] debugPrintEnvironment Synchrony working dir: C:\mystuff\eclipse-workspace\searchandpackage\target\confluence\home
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,565 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] debugPrintEnvironment C:\Program Files\Java\jdk1.8.0_121\jre\bin\java.exe -classpath C:\mystuff\eclipse-workspace\searchandpackage\target\container\tomcat8x\cargo-confluence-home\temp\2.1.0-release-confluence_6.5-1a01ab2d.jar;C:\mystuff\eclipse-workspace\searchandpackage\target\container\tomcat8x\cargo-confluence-home\webapps\confluence\WEB-INF\lib\h2-1.3.176.jar -Xss2048k -Xmx1g synchrony.core sql
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,857 INFO [ListenableFutureAdapter-thread-156] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled proxy port present: false
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,857 INFO [ListenableFutureAdapter-thread-156] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled app config synchrony.proxy.enabled: true
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,867 INFO [ListenableFutureAdapter-thread-156] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Base URL: http://localhost:1990/synchrony-proxy,http://localhost:1990/confluence/synchrony-proxy
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,867 INFO [ListenableFutureAdapter-thread-156] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Service URL: http://localhost:1990/synchrony-proxy/v1
[INFO] [talledLocalContainer] 2018-04-25 13:50:54,867 INFO [ListenableFutureAdapter-thread-156] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony Internal Service URL: http://127.0.0.1:8091/synchrony/v1

So, I went to the Collaborative Editing and saw that it was OFF.  So, why all this endless startup/stops?  Something I need to fix?  I decided to turn Collaborative edit ON in the hopes to turn it back off to see if this stops and now the spinner just spins endlessly.

Please help

[Al Johnson]

Well, I guess I have to kill it some other way.  I found this:

/rest/synchrony-interop/disable

but it doesn't work via the browser address bar.  You have to execute it via the REST Browser.