sounds like a bug - I wonder do you get the same issue in 4.0?
On 6/21/06, jerb <[EMAIL PROTECTED]> wrote:
I'm using 3.2 and I get different behavior when creating a connection using transport url - "list:(vm://brokername)" than when using "vm://brokername". The difference appears to be that the former always creates a new embedded broker while the latter will reuse an existing broker. The result is that clients intending to use "vm://brokername" as the transport won't be able to transmit messages to eachother if one of them was configured in a list. Looking at the code, the reason appears to be that the ActiveMQConnectionFactory looks into the brokerContext to check for an existing broker connector, while the CompositeTransportChannel does not. Why the difference in behavior? -- View this message in context: http://www.nabble.com/list-transport-with-vm-t1823631.html#a4973427 Sent from the ActiveMQ - User forum at Nabble.com.
-- James ------- http://radio.weblogs.com/0112098/
