Note that I have personally seen the HTTP transport consuming significant CPU resources in the past. Be sure to measure performance and watch CPU utilization. IIRC that's because the implementation frequently polls.
I recommend looking to an alternate approach. One I've implemented with great results in the past uses websockets to provide long-lived connections over HTTP-compliant connections that are supported by a large number of firewalls and proxies, while giving low message delivery latency. -- View this message in context: http://activemq.2283324.n4.nabble.com/HTTP-transport-tp4014555p4704936.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
