You'll have to check to see what the broker thinks is going on. So if the
broker dispatches messages up to the consumer prefetch limit, and the
consumer hasn't sent ack's back, the broker will not try to send any more
messages and your consumers will look hung.
On Thu, Aug 1, 2013 at 5:27 PM, Jma
Paddy, can you confirm CORS is indeed not allowed with the current
implementation?
I peeked at the code really quick and I don't see anything specific to same
origin policy configurations, but if you confirm it cannot be done
currently, then open a jira and we can get that in there.
On Fri, Aug 2
Hi -
I'm trying to connect to a broker that is in a different domain than
where my web app is originating from. Following is what I read from the
ActiveMQ documentation:
One thing worth noting is that web sockets (just as Ajax) implements the*same
origin policy*, so you can access only brokers
Let me summarize my observations so far (and I think all of these are bugs in
activemq-core-5.7.0):
1. Improper PFC kicking-in to persistent topic message publishers
When a durable topic subscriber(s) is (are) not consuming, *persistent*
message publishing is blocked (PFC) by exceeding topic's *pe
Hello, I'm hoping that someone would be able to help me understand why I am
having an issue with my applications usage of ActiveMQ under flow control
situations. I'm using 2 ActiveMQ 5.4.3 brokers using Open JDK 1.6,
configured with 5 queues each. I have 2 applications in separate JVMs
connecting
