cancel
Showing results for 
Search instead for 
Did you mean: 

Disabling tomcat shutdown port

Julien_Eluard
Confirmed Champ
Confirmed Champ

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.

1 ACCEPTED ANSWER

Not applicable

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

View answer in original post

2 REPLIES 2

Not applicable

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

Thanks fot the link!

Getting started

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.