03-26-2013 12:43 PM
It looks like when using -1 as tomcat shutdown port (nuxeo.server.tomcat-admin.port=-1 in nuxeo.conf) configuration check fails. -1 allows to disable the shutdown port and used in this doc.
Here is the exception I get:
Exception in thread "NuxeoProcessThread-0" java.lang.IllegalArgumentException: Invalid port: -1 at org.nuxeo.launcher.config.ConfigurationGenerator.checkPortAvailable(ConfigurationGenerator.java:1355) at org.nuxeo.launcher.config.TomcatConfigurator.checkNetwork(TomcatConfigurator.java:211) at org.nuxeo.launcher.config.ServerConfigurator.verifyInstallation(ServerConfigurator.java:586) at org.nuxeo.launcher.config.ConfigurationGenerator.verifyInstallation(ConfigurationGenerator.java:1237) at org.nuxeo.launcher.NuxeoLauncher.doStart(NuxeoLauncher.java:1204) at org.nuxeo.launcher.NuxeoLauncher$1.run(NuxeoLauncher.java:831) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)
Also setting nuxeo.force.generation=false still triggers the check, not sure if that's expected.
03-27-2013 05:41 AM
It's a bug: we pre-check ports at launch time so we don't try to use a port already in use, but this case wasn't taken into account.
See NXP-11318
03-27-2013 05:41 AM
It's a bug: we pre-check ports at launch time so we don't try to use a port already in use, but this case wasn't taken into account.
See NXP-11318
03-27-2013 10:55 AM
Thanks fot the link!
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.