-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
Using s2i to provide custom configuration doesn't work, as the s2i run script does not tell the launch script to start.
Creating an image with s2i logs just
-XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -XX:MaxMetaspaceSize=100m -XX:+ExitOnOutOfMemoryError Configuring Broker -z is true Creating Broker with args --silent --role admin --name broker --http-host 10.131.0.113 --java-options=-Djava.net.preferIPv4Stack=true --user username --password password --allow-anonymous --host 0.0.0.0 Creating ActiveMQ Artemis instance at: /home/jboss/broker Auto tuning journal ... done! Your system can make 3.52 writes per millisecond, your journal-buffer-timeout will be 284000 You can now start the broker by executing: "/home/jboss/broker/bin/artemis" run Or you can run the broker in the background using: "/home/jboss/broker/bin/artemis-service" start Copying Config files from S2I build '/opt/amq/conf/broker.xml' -> '/home/jboss/broker/etc/broker.xml' '/opt/amq/conf/jgroups-ping.xml' -> '/home/jboss/broker/etc/jgroups-ping.xml' Custom Configuration file 'BROKER_XML' is disabled Custom Configuration file 'LOGGING_PROPERTIES' is disabled
and then terminates.
- is cloned by
-
CLOUD-2658 [AMQ7] /usr/local/s2i/run missing the "start" argument in launch.sh invocation
- Closed