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 "Trần Tiến Đức (JIRA)" <ji...@apache.org> on 2018/12/25 08:24:00 UTC
[jira] [Updated] (MAILBOX-368) Implement a work queue for listeners
[ https://issues.apache.org/jira/browse/MAILBOX-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trần Tiến Đức updated MAILBOX-368:
----------------------------------
Description:
Following work done in MAILBOX-367 we will handle asynchronous execution for listener, as defined in API MAILBOX-364
{code:java}
interface EventBus {
... Registration register(Listener listener, Group group); ...
}
{code}
- Upon new group registration, RabbitMQEventBus attempts to create a queue per listener group, bounded to the exhange introduced in MAILBOX-367 .
- RabbitMQEventBus also registers a consumer executing the given listener group - bound to the listener group queue
For test:
- With a single RabbitMQDelegatingListener, ensure that global listeners are correctly executed
- With 2 RabbitMQDelegatingListener, ensure that all global listeners are executed at least once accross the cluster
was:
Following work done in MAILBOX-367 we will handle asynchronous execution for listener, as defined in API MAILBOX-364
```
interface EventBus {
...
Registration register(Listener listener, Group group);
...
}
```
- Upon new group registration, RabbitMQEventBus attempts to create a queue per listener group, bounded to the exhange introduced in MAILBOX-367 .
- RabbitMQEventBus also registers a consumer executing the given listener group - bound to the listener group queue
For test:
- With a single RabbitMQDelegatingListener, ensure that global listeners are correctly executed
- With 2 RabbitMQDelegatingListener, ensure that all global listeners are executed at least once accross the cluster
> Implement a work queue for listeners
> ------------------------------------
>
> Key: MAILBOX-368
> URL: https://issues.apache.org/jira/browse/MAILBOX-368
> Project: James Mailbox
> Issue Type: Improvement
> Reporter: Trần Tiến Đức
> Priority: Major
>
> Following work done in MAILBOX-367 we will handle asynchronous execution for listener, as defined in API MAILBOX-364
> {code:java}
> interface EventBus {
> ... Registration register(Listener listener, Group group); ...
> }
> {code}
> - Upon new group registration, RabbitMQEventBus attempts to create a queue per listener group, bounded to the exhange introduced in MAILBOX-367 .
> - RabbitMQEventBus also registers a consumer executing the given listener group - bound to the listener group queue
> For test:
> - With a single RabbitMQDelegatingListener, ensure that global listeners are correctly executed
> - With 2 RabbitMQDelegatingListener, ensure that all global listeners are executed at least once accross the cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org