Github user gemmellr commented on the issue:
https://github.com/apache/qpid-jms/pull/12
> Agreed its not ideal we have to do this, but this was found on epoll in
artemis (which you already have epoll implemented and defaulted to true) , as
such until netty improve the check then this check is worth while for the
interim unless you default epoll to false currently the client has the same
issue with epoll as found - https://issues.apache.org/jira/browse/ARTEMIS-1099
Given it seems it only happens if you use a 32bit JVM and only emits a
warning, I don't think its serious enough to introduce all that not-ideal code
for the existing epoll bits when noone has yet complained about it with the
client. This is however an opportunity to get it addressed in Netty instead
where it seems like it belongs.
> The classifier for the dependency for kqueue implementation is for osx
build, there isn't one currently for freeBSD or other derivaitves (osx being
bsd based), as such the check for the platform being osx, to be safe. E.g. our
case is we do have java clients that are on macOS.
I realise that the existing artifact is targetting OSX, but that could
change and its just another ugly check for us to fall afoul of later. Netty
better knows what the restrictions on its usage are than we do, it seems like
its availability check should be handling such things.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
