Nuxeo on OpenShift

[Julien_Eluard]

I'm trying to run nuxeo on OpenShift. As OpenShift restricts ports / bindable IPs I modified nuxeo.conf to fits those. Still it looks like a particular check performed by ConfigurationGenerator fails on OpenShift: see the call here.

I reproduced using a dumb example and indeed this particular calls fails with a "java.net.ConnectException: Permission denied" on OpenShift.

What would be the simplest/cleanest way (in this order :)) to work around this? Right now I cannot make nuxeo start on OpenShift.

Thanks!

[Florent_Guillau]

I tried OpenShift a few months ago and didn't have this problem. What full stack trace do you get? What's the IP used?

[Julien_Eluard]

Full stack I get is

[Florent_Guillau]

Is the / at the start of the address normal? I'm surprised it's there.

[Florent_Guillau]

Quick answer: not possible due to the OpenShift memory limitation to 512 MB in the free gears.

[Julien_Carsique · Accepted solution]

Simplest would be to add a configuration option (for nuxeo.conf or any nuxeo.defaults) to bypass the address check. However, are you sure Tomcat will be able to bind that address if it's not reachable?

What about the org.nuxeo.launcher.config.ConfigurationGenerator.checkPortAvailable(InetAddress, int) next check? Will it fail too and must also be bypassed?

Those checks were initially added to early detect the situations leading to the "Address already in use" error at server (Tomcat/JBoss) startup.

[Julien_Eluard]

I did a quick test and the next check (from checkPortAvailable(InetAddress, int)) works fine on OpenShift.

[Florent_Guillau]

Agreed, in my opinion the checkAddressReachable on a bind address is wrong, we'll probably remove it.

[Julien_Carsique]

[NXP-11306][1]

[Julien_Eluard]

Thanks for the ticket!