Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MB-804
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Gary Tully
Reporter: Dave Stanley
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
FUSE Message Broker

NetworkConnection initialization should be backed by an executor

Created: 19/Jan/11 06:52 PM   Updated: 01/Mar/11 04:14 PM
Component/s: broker
Affects Version/s: 5.4.2-fuse-00-00
Fix Version/s: 5.4.2-fuse-02-00

Environment: 5.4.x, All platforms

External Issue URL: https://issues.apache.org/jira/browse/AMQ-3195


 Description  « Hide
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.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Gary Tully added a comment - 01/Mar/11 01:00 PM

Gary Tully added a comment - 01/Mar/11 01:36 PM
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.