| Hi Jürgen,
In general the production mode is explicit when it comes to configuration. Nothing is started or activated by default. Everything has to be configured.
As Andreas wrote, in production mode no server roles are activated by default. A node has to be configured to actually start/activate the Jetty server. This can be done using the “-roles” argument as Andreas described or by tagging a node. In addition to that, the port/connector needs to explicitly configured in the Admin Console. If only http is required, you can also trigger the creation of a connector using the system property ‘org.osgi.service.http.port’ in the config.ini or as a launcher argument.
Andreas/Jürgen, I’d appreciate if you can take a first stab of bringing this into the wiki. I realized today that you aren’t the first ones that stumbled upon this.
-Gunnar
Am 30.10.2014 um 19:19 schrieb Jürgen Albert <j.albert@xxxxxxxxxxxxxxxxxx>:
Hi,
I have a server that should run in production mode with an external zookeeper. Thus I added gyrex.operation.mode=PRODUCTION to configuration/config.ini. The result is, that the server starts but seems to bind no connector.
Am I missing something or is this a bug?
Jürgen.
--
Jürgen Albert
Geschäftsführer
Data In Motion UG (haftungsbeschränkt)
Kahlaische Str. 4
07745 Jena
Mobil: 0157-72521634
E-Mail: j.albert@xxxxxxxxxxxxxxx
Web: www.datainmotion.de
XING: https://www.xing.com/profile/Juergen_Albert5
Rechtliches
Jena HBR 507027
USt-IdNr: DE274553639
St.Nr.: 162/107/04586
_______________________________________________
gyrex-dev mailing list
gyrex-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/gyrex-dev
|
