[
https://issues.apache.org/jira/browse/ARTEMIS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965109#comment-14965109
]
clebert suconic commented on ARTEMIS-266:
-----------------------------------------
I didn't add such option because --aio would still failback to NIO if the
library isn't found.
I think we should add a new option --nio to force NIO.
> Artemis creating instance concept of --aio switch is not flexible enough
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-266
> URL: https://issues.apache.org/jira/browse/ARTEMIS-266
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 1.1.1
> Environment: apache-artemis-1.1.1-20151020.030137-16-bin.zip on a
> RHEL 6.7 x86_64 machine
> Reporter: Frantisek Reznicek
> Priority: Minor
>
> Artemis creating instance concept of --aio switch is not flexible enough.
> The functionality of forcing configuration to use AIO with --aio switch is
> not flexible enough.
> We have three states there:
> * autodetection
> * force AIO with --aio
> * force to not use AIO
> I'd recomment to change to be able to force third option as well (this is in
> particular handy for QE).
> Thus I propose two options:
> a] keep --aio or change to --aio-cfg which would get additional argument
> (AUTO, AIO, NOAIO), where AUTO is default
> b] keep --aio as is and introduce --no-aio for forcing the third case (this
> is a bit awkward from command-line switch point of view, but keeps full
> backward compatibility)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
