chibenwa opened a new pull request, #1003: URL: https://github.com/apache/james-project/pull/1003
AMQP channel uses a lock to execute one RPC Shitty driver design, iterating the channel pool to get a channel without RPC looks like a dead end. At the very least we should not block the Netty event loop.... CF flame graph in the event loop:  CF AMQPChannel code: ``` private void doEnqueueRpc(Supplier<RpcWrapper> rpcWrapperSupplier) { synchronized(this._channelMutex) { boolean waitClearedInterruptStatus = false; while(this._activeRpc != null) { try { this._channelMutex.wait(); } catch (InterruptedException var6) { waitClearedInterruptStatus = true; } } if (waitClearedInterruptStatus) { Thread.currentThread().interrupt(); } this._activeRpc = (RpcWrapper)rpcWrapperSupplier.get(); } } ``` Getting tired of RabbitMQ driver and its fake reactive implementation. -- 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]
