how to use rabbitmq as messagebus or queue? #1526

Activity

1. niemyjski commented on Mar 25, 2024

   

   niemyjski

   on Mar 25, 2024

   Member

   More actions

   We probably need to take a pass at redoing all of configuration to be more explicit, but you should be able to do this two ways.

   1. Set the MessageBus connection string to provider=rabbitmq;CONNECTION_STRING_HERE
   2. Set the MessageBus connection string to provider=rabbitmq; then add rabbitmq to the connection strings app config / env section with the raw connection string

   cc @ejsmith
2. niemyjski

   self-assigned this

   on Mar 25, 2024
3. niemyjski

   added

   question

   documentation

   on Mar 25, 2024
4. sampsonye commented on Mar 25, 2024

   

   sampsonye

   on Mar 25, 2024

   Author

   More actions

   We probably need to take a pass at redoing all of configuration to be more explicit, but you should be able to do this two ways.

   1. Set the MessageBus connection string to provider=rabbitmq;CONNECTION_STRING_HERE
   2. Set the MessageBus connection string to ; then add rabbitmq to the connection strings app config / env section with the raw connection stringprovider=rabbitmq

   cc @ejsmith
   all dosn't work fine because exceptionless request connectionstring must like key=value patten
   
   ParseConnectionString() and BuildConnectionString() method working on it.
5. niemyjski commented on Mar 26, 2024

   

   niemyjski

   on Mar 26, 2024

   Member

   More actions

   Can you please add a sample connection string that can be bested. If you wouldn't mind adding a test and or updating this that would be a huge help. I know the cache one supports this, might have just been a miss.
6. sampsonye commented on Mar 27, 2024

   

   sampsonye

   on Mar 27, 2024

   Author

   More actions

   
7. sampsonye commented on Mar 27, 2024

   

   sampsonye

   on Mar 27, 2024

   Author

   More actions

   
8. niemyjski commented on Mar 27, 2024

   

   niemyjski

   on Mar 27, 2024

   Member

   More actions

   Can you paste that connection string here and also try escaping it with quotes?
9. niemyjski

   added a commit that references this issue on Apr 7, 2024

   Fixes #1526 - If provider connection string is specified use it.

   This issue will close once commit 92f1121 is merged into the 'main' branch.

   92f1121
10. niemyjski commented on Apr 7, 2024

    

    niemyjski

    on Apr 7, 2024

    Member

    More actions

    I was finally able to dig in and get this fixed. I've submitted a pr for the team to review.
11. niemyjski

    added

    bug

    help wanted

    and removed

    question

    documentation

    on Apr 7, 2024
12. niemyjski

    closed this as completedin 5033f18on Apr 7, 2024
13. niemyjski commented on Apr 7, 2024

    

    niemyjski

    on Apr 7, 2024

    Member

    More actions

    Thanks for logging this, this is fixed in a nightly build
14. niemyjski

    added a commit that references this issue on Apr 7, 2024

    Revert "Fixes #1526 - If provider connection string is specified use …

    ...

    This issue will close once commit 8dc70d7 is merged into the 'main' branch.

    8dc70d7
15. niemyjski

    reopened this on Apr 7, 2024
16. niemyjski commented on Apr 7, 2024

    

    niemyjski

    on Apr 7, 2024

    Member

    More actions

    I had to revert this change as it was a pretty big breaking change to configuration. We will address this shortly.
17. ejsmith

    added a commit that references this issue on Apr 9, 2024

    Fixes #1526 - If provider connection string is specified use it. (#1540)

    ...

    This issue will close once commit 5033f18 is merged into the 'main' branch.

    5033f18
18. niemyjski

    added 2 commits that reference this issue on May 19, 2026

    Fixes #1526 - If provider connection string is specified use it. (#1540)

    ...

    This issue will close once commit eec2a0b is merged into the 'main' branch.

    eec2a0b

    Revert "Fixes #1526 - If provider connection string is specified use …

    ...

    This issue will close once commit 8a46b75 is merged into the 'main' branch.

    8a46b75
19. niemyjski

    assigned

    Copilot

    on May 31, 2026
20. Copilot

    linked a pull request that will close this issueAdd technology-based infrastructure connection strings #2273on May 31, 2026
21. niemyjski commented on Aug 12, 2026

    

    niemyjski

    on Aug 12, 2026

    Member

    More actions

    Update: PR #2273 has been expanded into a compatibility-safe infrastructure configuration change and is ready for another review: #2273

    For new configurations, RabbitMQ can now be declared directly as a named technology connection string and will automatically supply MessageBus:

    EX_ConnectionStrings__RabbitMQ: amqps://user:password@rabbitmq:5671/%2F

    Raw amqp:// and amqps:// URIs are preserved, including encoded credentials, virtual hosts, query options, and optional wrapping quotes. The older forms remain supported too:

    EX_ConnectionStrings__MessageBus: 'provider=rabbitmq;server="amqps://user:password@rabbitmq:5671/%2F"'

    The PR also adds focused regression tests and self-hosting documentation, while retaining the existing Redis/Helm/Docker selectors that caused the earlier attempt to be reverted as breaking. RabbitMQ is supported for MessageBus; queues continue to use Azure Queues, SQS, Redis, or the local implementation.