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 2021/09/04 05:12:00 UTC
[jira] [Closed] (JAMES-3142) Removing an additional mailbox
listener
[ https://issues.apache.org/jira/browse/JAMES-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-3142.
---------------------------------
Resolution: Won't Fix
Please remove listeners manually within rabbitMQ admin web interface.
> Removing an additional mailbox listener
> ---------------------------------------
>
> Key: JAMES-3142
> URL: https://issues.apache.org/jira/browse/JAMES-3142
> Project: James Server
> Issue Type: Improvement
> Reporter: René Cordier
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> *Problem:*
> Given a running James cluster configured with additional listenerA When I do a rolling configuration change to remove listenerA Then James keeps posting events in the queue corresponding to listenerA without consuming it \{code}
> To summarize we can not remove additional listeners properly even with a restart.
> Impact: the queue keeps growing indefinitly eventually causing a rabbitMQ failure.
> This happened on UPN when we tried removing the SpamAssassin listener.
> *Solution*
> James could be sanitizing existing bindings upon start (removing the extra ones) but I'm worry about uneven configuration clusters. (serverA have the additional listener, not serverB)
--
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