Re: Error when Accessing a public queue

2015-05-19 Thread Jonasty
I solved it by replacing the vm for tcp and dropping the parameter -- View this message in context: http://activemq.2283324.n4.nabble.com/Error-when-Accessing-a-public-queue-tp4696639p4696648.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Network bridge throughput capped at default Socket buffer size

2015-05-19 Thread Christian Posta
What is the traffic across the WAN for an app other than ActiveMQ? Or what is the speed of the connection when done NOT over the WAN? WANs prioritize traffic, wonder if you're hitting a bottleneck in the WAN? On Tue, May 19, 2015 at 3:49 AM, Leung Wang Hei wrote: > Hi all, > > There seems to be

Network bridge throughput capped at default Socket buffer size

2015-05-19 Thread Leung Wang Hei
Hi all, There seems to be an invisible barrier in the socket buffer for MQ network bridge. We expect increasing tcp socket buffer size would give high throughput but the outcome is not. Here are the test details: - 2 brokers(A, B) bridged together over WLAN with 140ms network latency. - One s

Error when Accessing a public queue

2015-05-19 Thread Jonasty
*My broker configuration is the following:* queueRouteBuilder.setProcessor(processor); ActiveMQComponent component = new ActiveMQComponent(); component.setBrokerURL("vm://10.254.202.86:61616?broker.persistent=false"); context.addComponent("activemq", component); con