[AMQNET-281] NMS ActiveMQ and Stomp providers fail to Parse a Uri with params on both the outer and inner Uri's

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.4.1
• Component/s: ActiveMQ, Stomp
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 09/Sep/10 19:56
• Updated: 23/Sep/10 16:02
• Resolved: 23/Sep/10 16:02

Description

Some Uri string that are formatted as below can fail parse in the ConnectionFactory BrokerUri set property as the .NET Uri class returns the inner query string portion in this case.

activemq:failover:(tcp://${activemqhost}:61616?keepAlive=false&wireFormat.maxInactivityDuration=1000)"
activemq:failover:(tcp://${activemqhost}:61616?keepAlive=false&wireFormat.maxInactivityDuration=1000)?connection.asyncclose=false"

In the first Uri the Query string returned is:

?keepAlive=false&wireFormat.maxInactivityDuration=1000)

and in the second its

?keepAlive=false&wireFormat.maxInactivityDuration=1000)?connection.asyncclose=false

We need to modify the provider ConnectionFactory code to ensure that it doesn't use the inner Query params from the composite Uri.