activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clebert Suconic <>
Subject Re: Artemis 1.5.0 fails to discover libAIO on Linux, falls back to NIO
Date Mon, 12 Dec 2016 17:00:03 GMT
Perhaps we used a newer Linux kernel (than yours) to compile the
library and it wasn't compatible with your libc.

you could compile the library yourself from the source distribution.

I recommend you moving straight to 1.5.1 though. It's already tagged
and I made the upload today. I'm just waiting the release to hit the
mirrors to send the news. But you can find it on maven central for

this is a link to how to compile the native library from sources:

On Mon, Dec 12, 2016 at 11:34 AM, mlange <> wrote:
> I have a RHEL 6.7 server wich has LibAIO installed, using Java 1.8.0_102
> Artemis 1.4.0 finds and uses it with no problem, as this log line shows:
> 17:18:30,060 INFO  [org.apache.activemq.artemis.core.server] AMQ221012:
> Using AIO Journal
> When I create a broker with the same parameters on the same machine, but
> instead using Artemis-1.5.0 it fills in NIO in the broker.xml; When I change
> that by hand to ASYNCIO I get the following in the log:
> 15:46:04,805 WARN  [org.apache.activemq.artemis.core.server] AMQ222018: AIO
> was not located on this platform, it will fall back to using pure Java NIO.
> If your platform is Linux, install LibAIO to enable the AIO journal
> (I realize that having NIO in the broker.xml itself is a sign that the Linux
> AIO library could not be found)
> Yum shows that libaio.x86_64-0.3.107-10.el6 is installed.
> is this a bug, or some other mismatch I made?
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

Clebert Suconic

View raw message