activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: ActiveMQ duplex network connector dead lock [5.13.1, 5.11.1]
Date Mon, 07 Mar 2016 04:55:38 GMT
You can use two non-duplex connections, one from each broker.  This is
advantageous in some network configurations (e.g a pair of brokers) because
it lets you reuse the same configuration on multiple brokers (with a little
placeholder substitution) and disadvantageous in others (e.g. a
hub-and-spoke topology) because it forces both sides to be aware of the
connection between them.

But even if it complicates your config slightly, it'll still be better than
what you're hitting now.

Tim
On Mar 6, 2016 6:44 PM, "yang.yang.zz" <yang.yang.zz@outlook.com> wrote:

> Hi:
>
> We ran into this dead lock since upgrade to 5.11.1. In short, this dead
> lock
> happens on network connector when "duplex" is set to "true". For details of
> replicating this defect, see my earlier post  here
> <
> http://activemq.2283324.n4.nabble.com/5-13-1-message-blocked-td4708592.html
> >
>
> I also found an unresolved defect  AMQ-5260
> <https://issues.apache.org/jira/browse/AMQ-5260>   which has the same
> symptom. It looks like this issue could also be found in 5.9.x and 5.10.x.
>
> I'm wondering, is there a way to workaround this dead lock without
> modifying
> the source code? For example, is there an alternative 2-way communication
> configuration instead of using duplex?
>
> Thanks,
> -Yang
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-duplex-network-connector-dead-lock-5-13-1-5-11-1-tp4708952.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message