-
When using Event Publication Registry in combination with Event externalization to RabbitMQ (AMQP), the entry in the registration for externalize listener is marked completed even when the message fai…
-
When publishing to *Direct*, *Topic* or *Fanout* exchange (e.g.: `amqp://guest:guest@localhost/myExchange?type=topic`) no *Queue* and no *Queue Binding* needs to be done. Only simple publish is suffi…
-
# Summary
It would be extremely useful if a DAG could give up if argo already knows the end result will be failure. Currently the failFast option will stop scheduling dependencies if there has been…
-
The DMF API seems to behave like a request response API.
I was really hoping true publish subscribe behaviour would be possible; for example I want to listen for all and any changes to targets with…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
I need to create an API that will a…
Misiu updated
1 month ago
-
Retry with delays for AMQP messages. Environment variable: AMQP_PUBLISH_RETRY_DELAY, AMQP_PUBLISH_RETRY_ATTEMPTS.
Defaults: AMQP_PUBLISH_RETRY_DELAY - 100ms AMQP_PUBLISH_RETRY_ATTEMPTS - 10 Java AMQ…
-
Note that dependency: node-amqp-connection-manager currently has a reported bug (possibly?) and does not currently handle drain events. While it guarantees receipt of all published messages, it does n…
-
With Servicebus 1.0 Java client, one can only send message with AMQP Data which limits the interop with other AMQP clients. Other AMQP sections should be supported for main scenarios like.
- String…
-
We're trying to consume Azure Service Bus in a Node application. Our requirement is to fetch multiple messages from a queue.
Since Azure SDK for Node doesn't support batch retrieval, we decided to …
-
That way the messages will not crop up in an unused queue when there is no coordinator,
and there can be multiple consumers of the messages instead of just one.
Requires changes in all the partici…