Is the PFC kicking-in at the bridge? In my experience, PFC on a bridge often doesn't clear itself. When that happens, stack traces on the two brokers show that both brokers are blocked on attempts to send messages to one-another. Taking a few such traces over a period of time should help to determine whether that's a stuck state or not.
As I mentioned above, PFC blocks the entire connection. Blocking the entire connection for a bridge is a bad thing because that blocks all message flow between the brokers. One possible cause here is slow consumption. It's an unwritten rule with ActiveMQ that consumers must be fast enough to keep up with producers. PFC may prevent problems in that case, but I've seen it fail to do so. On the other hand, perhaps tuning the PFC settings is needed. Another thought is to not pass entire large files through ActiveMQ and instead place them somewhere accessible to both ActiveMQ clients, then simply pass the location (maybe URL) to access the file. Hope this helps. Perhaps Gary can speak to settings that might prevent the bridge from blocking on PFC. He helped me in the past with such a situation. -- View this message in context: http://activemq.2283324.n4.nabble.com/Is-Producer-Flow-Control-Necessary-When-Sending-Persistant-Messages-tp4676925p4676955.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
