There hasn't been a fix to artemis-native itself so you'll still need to
work-around this problem on Ubuntu deployments. My recommendation would be
to simply create a symlink as is done for Docker, e.g.:
ln -s /usr/lib/x86_64-linux-gnu/libaio.so.1t64 /usr/lib/libaio.so.1
I went ahead and created a Jira [1] to track this.
If you want to request a Jira account go here [2].
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-5190
[2] https://selfserve.apache.org/jira-account.html
On Thu, Nov 28, 2024 at 6:42 AM Gašper Čefarin <gasper.cefa...@actual-it.si>
wrote:
> Hello,
>
>
> I see the below mentioned issue (email from 7th june) has been solved for
> docker
>
>
> https://issues.apache.org/jira/browse/ARTEMIS-5055
>
> were any fixes included for non docker installations on ubuntu24 as well?
>
> also, it seems my message has gone unnoticed since the issue on jira
> appears in september, 3 months later.
> if at all possible, i'd also like to ask for a jira account to be able to
> report bugs there.
>
> Regards
>
>
> [image: 1658227403484]
> Gašper Čefarin
>
>
> *Systems Engineer *Ferrarska ulica 14, 6000 Koper – Slovenia
> M: +386 51 281 905
> W: http://www.actual-it.si
>
>
> ------------------------------
> *From:* Gašper Čefarin <gasper.cefa...@actual-it.si>
> *Sent:* 07 June 2024 16:38
> *To:* users@activemq.apache.org
> *Subject:* ASYNCIO problems on Ubuntu 24
>
>
> In Ubuntu24 package name for libaio1 has changed:
> https://packages.ubuntu.com/source/noble/libaio
>
> ArtemisMQ doesn't find the library and falls back to NIO.
>
> The libaio is now available under:
> */usr/lib/x86_64-linux-gnu/**libaio.so -> libaio.so.1t64.0.2*
>
> dirty fix which seems to work:
>
> *cd /usr/lib/x86_64-linux-gnu/ cp libaio.so libaio.so.1*
>
>
>
>
> [image: 1658227403484]
> Gašper Čefarin
>
>
> *Systems Engineer *Ferrarska ulica 14, 6000 Koper – Slovenia
> M: +386 51 281 905
> W: http://www.actual-it.si
>
> NOTICE - NOT TO BE REMOVED.
> This e-mail and any attachments are confidential and may contain legally
> privileged information and/or copyright material of Actual I.T. or third
> parties. If you are not an authorised recipient of this e-mail, please
> contact Actual I.T. immediately by return email or by telephone or
> facsimile on the above numbers.
> You should not read, print, re-transmit, store or act in reliance on this
> email or any attachments and you should destroy all copies of them.
>
