Hello,
I am currently testing ways to run the OSGI enRoute QuickStart tutorial
(as an executable jar straight to a Cloud Foundry java_buildpack) on IBM
Bluemix but, whilst the sample works perfectly locally it fails when
deployed on Bluemix.
A binding time-out between the cloud container and the app's embedded
Jetty is the cause of the failure.
The timeout occurs because Jetty is started with its default port (or
one set manually) whilst the Bluemix container is assigned a random port
number each time the app is deployed/re-staged (effectively, each time
the container is restarted).
After Googling without much success, and being new to OSGI, I am left
quite confused by this.
I therefore would be very grateful if anyone could cast some light on
what would be the best approach to assign the freshly generated
container's random port to Jetty (taking into account that the
container's port number is a system environment variable accessible via
code) each time the container is started/restarted.
Thanks in advance.
--
*Loic**
*
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
