[ 
https://issues.apache.org/jira/browse/ARTEMIS-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved ARTEMIS-4538.
-------------------------------------
    Fix Version/s: 2.32.0
       Resolution: Fixed

I updated things so the existing note about configuring transport options for 
TLS, with pointers to related options page and example, now use the 'alert 
style' note so it is more prominent.

> Make note around amqp broker-connection URI transport options more prominent
> ----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4538
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4538
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>            Reporter: John Clifford
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.32.0
>
>
> Make existing note around amqp-broker-connection URI transport options, such 
> as for enabling and configuring TLS, more prominent.
>  
> ===============
> Original Description:
> The [Artemis 
> documentation|https://activemq.apache.org/components/artemis/documentation/latest/amqp-broker-connections.html]
>  explains how to make a connection for mirroring using the 
> {{<amqp-connection>}} configuration. However, it isn't clear what format the 
> connection URI takes. In particularly, it isn't clear how to configure it to 
> use TLS.
> I understand that the URI format is, in fact, the same as that used by other 
> Artemis network connections. I would not have guessed this, because Artemis 
> does not use AMQP for any of these other connections, and I just assumed that 
> AMQP mirroring connections would be configured differently.
> So I think all that is needed here is one additional line explaining this, 
> and perhaps linking to the relevant section of the docs. A specific example 
> of configuring a mirror connection using TLS would, I think, provide useful 
> additional help.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to