William Sperlazza created ARTEMIS-5055:
------------------------------------------

             Summary: AIO not available in official ubuntu docker image
                 Key: ARTEMIS-5055
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5055
             Project: ActiveMQ Artemis
          Issue Type: Bug
          Components: ActiveMQ-Artemis-Native
    Affects Versions: 2.37.0, 2.36.0
            Reporter: William Sperlazza
            Assignee: Clebert Suconic


libaio changed their package name as was addressed here: 
[https://github.com/apache/activemq-artemis/commit/86f36e95b09c709fb7e4af33f4a535f9a80d7221]

 

But the native LibaioContext link is still trying to reference libaio.so.1, as 
seen in startup logs with debug enabled:
{quote}

2024-09-18 15:40:43,807 DEBUG 
[org.apache.activemq.artemis.nativo.jlibaio.LibaioContext] artemis-native-64 -> 
not possible to load native library
java.lang.UnsatisfiedLinkError: 
/opt/activemq-artemis/bin/lib/linux-x86_64/libartemis-native-64.so: 
libaio.so.1: cannot open shared object file: No such file or directory{quote}
I think the link created 
[here|https://github.com/apache/activemq-artemis-native/blob/02ad87f08395993ae417ce75bf8ce78a3bc23e0a/src/main/c/CMakeLists.txt#L80C1-L80C22]
 is stale, and a simple rebuild of artemis-native may be all that's needed? 
Maybe the [dockerfile needs updating 
there|https://github.com/apache/activemq-artemis-native/blob/02ad87f08395993ae417ce75bf8ce78a3bc23e0a/src/main/docker/Dockerfile-ubuntu#L36]
 too though.

NOTE: This only affects the ubuntu image; alpine is fine.

 

The workaround is to either use the alpine official image instead, or create a 
symlink to the old library name in a Dockerfile based on the official image:


{quote}RUN ln -s  /lib/x86_64-linux-gnu/libaio.so.1t64 
/lib/x86_64-linux-gnu/libaio.so.1
{quote}
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to