Hi, I'm unable to run installs like that in my build, but I have the .so files for libaio so I should be able to run an AIO journal if I can set up the environment correctly. Thanks for the suggestion, but I really need something more in line with the approach I laid out.
Thanks, Matthew On Thu, Jan 27, 2022 at 4:20 PM Vilius Šumskas <vilius.sums...@rivile.lt> wrote: > Hi, > > most of the distributions have libaio packaged and ready. You just need to > "dnf install" or "apt-get" it in your container image. > > -- > Vilius > > -----Original Message----- > From: Matthew Harris <harrisman1...@gmail.com> > Sent: Thursday, January 27, 2022 11:14 PM > To: users@activemq.apache.org > Subject: Difficulties finding libaio > > Hi, > > I'm trying to containerize apache-artemis-2.20.0, and right now I'm > working on adding libaio to the container so I can use an AIO journal for > faster performance. I stored the .so files for libaio in a directory in the > container, and I set the LD_LIBRARY_PATH environment variable to point to > the directory containing those files. > > However, when I spin up the container and run the broker, it can't find > libaio and defaults to an NIO journal. I see here: > > https://activemq.apache.org/components/artemis/documentation/1.1.0/using-server.html#library-path > that java.library.path is specified automatically in the scripts, so I'm > assuming why the JVM isn't using the environment variable to find libaio. > > I also see that there's a --java-options argument that can be provided > when the broker is created. Is there a way to overwrite or add a path to > java.library.path this way? It's been a long time since I've worked with > Java so I'm a little lost as to how to point this to the correct directory > and load libaio. > > Thanks, > Matthew >
