Details
-
Type:
Enhancement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.4.2-fuse-00-00
-
Fix Version/s: 5.4.2-fuse-02-00
-
Component/s: broker
-
Labels:None
-
Environment:5.4.x, All platforms
-
Similar Issues:
-
External Issue URL:
Description
We have a broker that connects to a large number of peers. It appears network connection establishment is done by a single thread.
This is an enhancement to get the network connector setup handled by a an executor so we can
can have concurrent network connection establishment. This is really to handle the case where
one network connection is slow to establish, it doesn't hold up communication
with other peers in the network of brokers.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
fix on 5.4.x fuse branch, will be in tonight's snapshot
new attribute on the broker: networkConnectorStartAsync. when set to true, network connectors will be initiated in parallel, async to a broker start. So fast ones will complete quickly and the broker will start quickly. Slow ones will just block a thread dedicated to that network connector start.
Gary Tully
added a comment - fix on 5.4.x fuse branch, will be in tonight's snapshot
new attribute on the broker: networkConnectorStartAsync. when set to true, network connectors will be initiated in parallel, async to a broker start. So fast ones will complete quickly and the broker will start quickly. Slow ones will just block a thread dedicated to that network connector start. 
link to apache issue https://issues.apache.org/jira/browse/AMQ-3195