Re: Roundup of the configuration files

I believe this is still problematic: /app/${activemq.data}/kahadb I expect ${activemq.data} to be expanded to the actual value > On Jun 22, 2021, at 3:37 PM, Fabrice Triboix > wrote: > > I think I didn't miss it, but for some reason it doesn't get attached. So > here is a copy/paste: >

Re: Roundup of the configuration files

I think I didn't miss it, but for some reason it doesn't get attached. So here is a copy/paste: ​FROM openjdk:11-jre # Environment variables: version and tarball stuff ENV ACTIVEMQ_VERSION 5.16.2 ENV ACTIVEMQ apache-activemq-$ACTIVEMQ_VERSION ENV ACTIVEMQ

RE: Artemis clusters and large messages

Justin, > FWIW, the cluster-connection does have its own min-large-message-size > configuration element. It is actually worth a lot. I did not look at these details because the URL parameter already seemed like the correct choice. > Do you still see this problem when you use that? No, there is

Re: Roundup of the configuration files

It looks like I missed the Dockerfile, sorry about that. Here it is! From: Fabrice Triboix Sent: 22 June 2021 20:27 To: users@activemq.apache.org Subject: Re: Roundup of the configuration files CAUTION: This email originated from outside of the organization.

Re: Roundup of the configuration files

Hi Matt, Please find attached my Dockerfile and docker-compose file. Also included is the "conf" directory I am mounting inside the container to configure ActiveMQ. Hopefully you should be able to reproduce the problem. Here is the full log when I run docker-compose up​ $ docker-compose up

Re: Roundup of the configuration files

Flying blind here.. without more detailed logs or information there isn’t enough information to point to a root cause. I can confirm that people have run ActiveMQ in Docker containers for years, so I do not suspect you are running into a bug at this point. I’d look into this line next--

Re: Roundup of the configuration files

Hi Matt, No, I am not using a volume at the moment. The data directory that I am using is /app/data​ and is owned by the activemq​ user and activemq​ group with 755 permissions. ActiveMQ runs as the activemq​ user. ActiveMQ clearly can create files there: activemq@7a5313d69a74:/app/data$ ls

Re: Roundup of the configuration files

Are you using a volume? Could be permissions related that ActiveMQ is unable to get a lock on the filesystem. > On Jun 22, 2021, at 8:57 AM, Fabrice Triboix > wrote: > > Hi Matt, > > I am running ActiveMQ as a Docker container, so I am positively certain that > (1) there are no other

Re: Roundup of the configuration files

Hi Matt, I am running ActiveMQ as a Docker container, so I am positively certain that (1) there are no other ActiveMQ processes and (2) the "data" directory is empty at startup. Additionally, when I add back all the other configuration files (i.e. the files in the conf​ directory of the

Re: Roundup of the configuration files

Is that filesystem a local disk (i.e. exclusive to the host) or an NFS share (i.e. the file could be locked by a process running on another host)? If the latter, lsof wouldn't show processes from other hosts, so you'd want to run the command from all hosts where ActiveMQ is installed and might be

Re: Roundup of the configuration files

The filesystem locking is simply delegated to the OS. Double check you do not have a second ActiveMQ process that was left running unintentionally during the config testing. If it is on Linux, you can use the ‘lsof’ command to look for the process that has the kahadb/lock file locked. -Matt

Re: Roundup of the configuration files

Hello Matt, I am using a subset of the configuration files found in the the conf​ directory of the official ActiveMQ release available here: https://archive.apache.org/dist/activemq/5.16.2/apache-activemq-5.16.2-bin.tar.gz The configuration files I kept are: * activemq.xml * jetty.xml