tabish121 commented on pull request #45: URL: https://github.com/apache/qpid-jms/pull/45#issuecomment-953985565
> @gemmellr > > Right now I'm not enforcing that a pooled (shared) event loop group matches the configured transport event loop type that is borrowing it, meaning that Netty woudl fail on transport connect because of channel/event loop mismatch, but I suppose this is not a valid use case I'm not particularly fond of one configuration option being able to cause breakage should another connection in the same VM have chosen not to use the same native (or not) transport type. It might seem benign now but guess whose going to have to support the case when it comes up later. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
