Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
0.43.0
-
None
Description
The client supports using the Netty Epoll and Kqueue native transports. In envs not supported by the native impls, or when configuration does not enable them (if available), the client uses Netty's NIO transport.
In certain cases the native bits can present issues (e.g doing AOT compilation of native images, or some OSGi uses eg QPIDJMS-400). Some of these can be avoided by substituting the non-functional java-only base dependency jars in for their platform-specific variants, but it would be nice to isolate use of these bits inside a utility class that encompasses their use and actually permits their absence at runtime to facilitate end usage exclusion.
Attachments
Issue Links
- incorporates
-
QPIDJMS-400 qpid-jms-client OSGI metadata should use resolution:="optional" for io.netty.channel.epoll and io.netty.channel.kqueue
- Closed