You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/07/07 10:17:00 UTC
[jira] [Commented] (JAMES-3299) IMAP SELECT hung because of
RabbitMQ queue binding
[ https://issues.apache.org/jira/browse/JAMES-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152621#comment-17152621 ]
Benoit Tellier commented on JAMES-3299:
---------------------------------------
https://github.com/linagora/james-project/pull/3548 solves the issue by adding a timeout
> IMAP SELECT hung because of RabbitMQ queue binding
> --------------------------------------------------
>
> Key: JAMES-3299
> URL: https://issues.apache.org/jira/browse/JAMES-3299
> Project: James Server
> Issue Type: New Feature
> Components: eventbus, IMAPServer, rabbitmq
> Reporter: Benoit Tellier
> Priority: Major
> Labels: bug, perf
> Attachments: Capture d’écran de 2020-07-07 08-14-56.png, Capture d’écran de 2020-07-07 08-16-30.png, Capture d’écran de 2020-07-07 08-21-39.png
>
>
> On one of our production instances, we have 6 select being hung. Investigations based on the flame graphs shows a RabbitMQ binding operation never completes
> See attavched glowroot slow traces and flame graphs.
> A reasonable timeout should be position to prevent such hangs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org