Hello.
Now when Java client supports NIO, it provides for lots and lots connections to be managed with a handful of threads.
However how does it work if each client connection requires its own client certificate (and consequently - an SSL context)?
If I read the code correctly, it is not possible because sslContext is passed to SocketChannelFrameHandlerFactory when it is initialised which happens only for the first connection.
If I am right, and the current client does not allow that - is it something just overlooked / low priority or was it a conscious decision to not support it for some reason?
Is there a known way to work around it and still use NIO?
I am thinking of a stress-test for RabbitMQ server for which lots and lots of client connections need to be established. But to simulate the real life situation, these better be different clients - each with its own SSL certificate/username. Doing that with NIO-enabled client in theory allows more client connections from a single machine because only a few threads are required to maintain them compared to thousands threads with the old client.
Many thanks.
Dmitry