[
https://issues.apache.org/activemq/browse/AMQNET-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-261.
---------------------------------
Resolution: Fixed
Fixed in trunk. Can now handle a wider range of Composite Uri formats. All
the Connection options specified on the Uri are now applied even when failover
is used.
> NMS URI handling in URISupport needs improvement.
> -------------------------------------------------
>
> Key: AMQNET-261
> URL: https://issues.apache.org/activemq/browse/AMQNET-261
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Affects Versions: 1.3.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 1.4.0
>
>
> The URI handling in NMS that allows for composite URIs and for setting
> options via the URI needs some work.
> 1. When setting options for the connection when a Failover URI is specified
> you receive and exception because the options aren't filter out based on the
> prefix, so for instance a value of connection=asyncSend=true will cause an
> exception in the failover URI case but not in a plain TCP uri case. Example:
> The following URI additional test case added to NMSConnectionFactoryTest
> should work, but it gives an exception.
> {noformat}
>
> [Row("activemq:failover:(tcp://${activemqhost}:61616)?connection.asyncSend=true")]
> {noformat}
> 2. Those referring to the AMQ docs will assume that URIs like the one's below
> should work but will get an exception instead.
> {noformat}
>
> failover://(tcp://localhost:61616,tcp://remotehost:61616)?initialReconnectDelay=100
> failover://tcp://primary:61616
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
