server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true;key-store-path=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true;key-store-path=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true;key-store-path=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port? key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URL as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 55 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 36 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 36 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 36 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port?key1=value1&key2=value2 ) to customize the underlying transport Netty transport. Using JMS 55 Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URL as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path

server(s). Each scheme has a specific set of properties which can be set using the traditional URL query string format (e.g. scheme://host:port? key1=value1&key2=value2 ) to customize the underlying transport regarding the Netty transport. Note if you are using the tcp scheme and multiple addresses then a query can be applied to all the url's or just to an individual connector, so where you have (tcp://remote-host1:5445 are passed straight through to the underlying transport. These are set on the URI as part of the query, like so: tcp://localhost:61617?sslEnabled=true&keyStorePath=/path