Github user michaelandrepearce commented on the issue:
https://github.com/apache/qpid-jms/pull/12
Hi @gemmellr
> I don't think the various environment etc checking being done really
belongs in the client, it seems like that stuff belongs in Netty if the
isAvailable() checks it offers aren't actually sufficient.
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
> Similarly it feels a little odd making it check for being on a Mac when
KQueue is really for BSD rather than OSX specific, and they might open up
support for others later, again it feels like Netty is better placed to be
checking that type of thing.
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.
> also think that if added the KQueue bit would be better set off by
default for now and flipped later on. It's very new in Netty itself, whereas
the epoll stuff had time to mature before it was added. Linux is also probably
the primary platform we test and use the client on, whereas we don't really
test on OS X at all (though I shall change that shortly), so sticking to the
NIO bits by default there seems wiser for now.
Sure this make sense we can make it default to false.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
