activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <>
Subject [jira] Resolved: (AMQ-1388) Make NetworkConnectors two-sided
Date Mon, 08 Oct 2007 05:30:23 GMT


Rob Davies resolved AMQ-1388.

    Resolution: Duplicate

This is a duplicate of
And is now fixed in 5.0 - set the duplex property on the network connector to true - see:

> Make NetworkConnectors two-sided
> --------------------------------
>                 Key: AMQ-1388
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: Ron Pressler
>            Assignee: Rob Davies
> Consider the following scenario:
> Several machines communicate using topics, using a hub-and-spoke topography, but instead
of having all messages go through a central broker, each machine has an embedded vm broker
to enable efficient intra-machine communication.
> This is a common architecture.
> Currently, to support such an architecture, if we want to allow dynamic addition of machines,
we need to configure both a network connector on each machine to connect to the central hub,
a tcp transport connector on the hub (to allow remote connections), as well as a multicast
discovery on the central hub and a tcp connector on each machine to allow the hub to connect
back to it.
> This is redundant, because the network connector from the vm broker to the central hub
should suffice to deliver messages in both directions, thus also making the discovery unnecessary
and the connections easier to maintain and monitor.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message