|
If you were logged in you would be able to see more operations.
|
|
|
ActiveMQ
Created: 26/Feb/07 11:43 AM
Updated: 05/Mar/07 08:26 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
4.0,
4.0.1
|
| Fix Version/s: |
5.0.0,
4.1.1
|
|
|
When you depend on the brokers to flow control your producers, the brokers are usually running with usage managers at 100%. Now if use this in network of brokers configuration it is very easy to get into a scenario where the brokers network bridges lock messages to send to the next broker but bock on the send and thus create a network deadlock.
|
|
Description
|
When you depend on the brokers to flow control your producers, the brokers are usually running with usage managers at 100%. Now if use this in network of brokers configuration it is very easy to get into a scenario where the brokers network bridges lock messages to send to the next broker but bock on the send and thus create a network deadlock. |
Show » |
|
Improvement
Resolved
Major
Avoid Network Deadlocks if possible
http://svn.apache.org/viewvc?view=rev&rev=511085
- enabled flow control again on network producers, but now use the sync acking on queues to avoid blocking the network connection. Takes advantage of the fix to AMQ-1123 solve deadlocks at the network bridge.
- disabled flow control on network producers
http://svn.apache.org/viewvc?view=rev&rev=511080