Hi Alex, you´re right, reloading after restart will get it back to work. Thanks for your explanation. Is there a schedule for the patch you mentioned?
For others facing the same problem: Meanwhile I found out that appending a "?ClientId=YourClientID" to the GET and POST urls (for either REST-API or AJAX-API [uses REST-API]) will prevent this problem from showing up. I guess this will bypass the automatic id assignment by the broker (via cookie). It seems to work very reliably now. ActiveMQ is so fast that I can use it for a real-time application (an interactive whiteboard). The broker in the middle allows my clients (mobiles) behind NAT/PAT to be reachable (push via ActiveMQ HTTP long-poll). I am very content with this now. Best regards -- View this message in context: http://activemq.2283324.n4.nabble.com/Beginner-problem-Too-many-consumers-on-queue-after-browser-restart-tp2719286p2762430.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
