[
https://issues.apache.org/jira/browse/JAMES-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3864.
-------------------------------
Resolution: Fixed
The PR has been merged to fix this issue.
What has been considered at the end is that the vhost should be declared in the
uri. The vhost parameter in rabbitmq.properties is still present, but only used
in special cases where there is bad formatted URIs making parsing not feasible
(like with characters like '_')
> Unify vhost management with queues and RabbitMQ
> -----------------------------------------------
>
> Key: JAMES-3864
> URL: https://issues.apache.org/jira/browse/JAMES-3864
> Project: James Server
> Issue Type: Improvement
> Reporter: René Cordier
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Actually in James we have our queues that get assigned to the correct vhost
> on rabbitmq but in two different ways:
> - via the uri parameter in rabbitmq.properties, like:
> {noformat}
> amqp://{user}:{password}@{rabbit_host}:{rabbit_port}/{vhost}
> {noformat}
> - via the parameter `vhost` in rabbitmq.properties (like for the mail queues)
> It's not really logical and confusing for users in general. We should:
> - agree on one unified way to get the vhost for all queues (uri parsing or
> vhost parameter)
> - refactor the code following the consensus on the solution
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
