Re: Mounting custom activemq config with custom docker image

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Mounting custom activemq config with custom docker image

Tim Bain
Is a log file being written? If so, it means the JVM came up at least
enough to load Log4J, and the log file should have useful information about
why the broker exited. If not, it means that the JVM is failing to launch
due to some fundamental reason (not enough RAM for the amount of heap
requested, for example, or JARs missing from the classpath, or...), and
tbat reason will probably be unrelated to ActiveMQ.

Tim

On Jul 9, 2018 10:40 AM, "avmpt" <[hidden email]> wrote:

I am having some issues with activemq when I try and run a custom config
through a custom image. To build my custom image I simply use the following
Dockerfile

FROM webcenter/activemq:5.14.3
COPY activemq.xml /opt/activemq/conf/

However when I use my custom image to launch a service on Marathon I see the
following error:

Registered docker executor on 10.0.5.220
Starting task activemq-active-broker.9e85fada-8390-11e8-834b-4e6b8a7e5d7e
2018-07-09 15:56:33,722 CRIT Supervisor running as root (no user in config
file)
2018-07-09 15:56:33,722 WARN Included extra file
"/etc/supervisor/conf.d/activemq.conf" during parsing
2018-07-09 15:56:33,722 WARN Included extra file
"/etc/supervisor/conf.d/cron.conf" during parsing
2018-07-09 15:56:33,729 INFO RPC interface 'supervisor' initialized
2018-07-09 15:56:33,729 CRIT Server 'unix_http_server' running without any
HTTP authentication checking
2018-07-09 15:56:33,729 INFO supervisord started with pid 1
2018-07-09 15:56:34,732 INFO spawned: 'cron' with pid 16
2018-07-09 15:56:34,733 INFO spawned: 'activemq' with pid 17
2018-07-09 15:56:35,837 INFO success: cron entered RUNNING state, process
has stayed up for > than 1 seconds (startsecs)
2018-07-09 15:56:35,837 INFO success: activemq entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-07-09 15:56:35,837 INFO exited: activemq (exit status 1; not expected)
2018-07-09 15:56:36,840 INFO spawned: 'activemq' with pid 93
2018-07-09 15:56:37,910 INFO success: activemq entered RUNNING state,
process has stayed up for > than 1 seconds (startsecs)
2018-07-09 15:56:37,911 INFO exited: activemq (exit status 1; not expected)
2018-07-09 15:56:38,913 INFO spawned: 'activemq' with pid 174
...

ActiveMQ will continuously get killed and restart and I'm not sure what the
reason is. I think it might be because of the way I mount the config (i'm
mounting it after the base image completes running?) but i'm not entirely
sure. Any ideas on what I should be looking into? Thanks!






--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html