activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: JMX and NetworkBridge
Date Tue, 10 Jul 2012 21:17:25 GMT
So the idea is that you use the stop method on the, so on an individual
bridge created by the network connector. There are two mbean in the
mix. The parent
and the nested NetworkBridgeView.

static discovery of the networkConncetor should trap the stop and
initiate a restart.

Note: you should not use failover with static: discovery, let the
static discovery deal with any reconnect issues.
see: for more detail

On 10 July 2012 21:43, billy <> wrote:
> It might help if I show you a piece of my active.xml file that sets up the NetworkBridges.
>         <networkConnectors>
>             <networkConnector name="DwhBridge" duplex="true" uri="static:(failover:(tcp://dwh:61616))"
>             <networkConnector name="EdiBridge" duplex="true" uri="static:(failover:(tcp://edi:61616))"
>         </networkConnectors>
> From: billy [via ActiveMQ] []
> Sent: Tuesday, July 10, 2012 3:13 PM
> To: Billy Buzzard
> Subject: Re: JMX and NetworkBridge
> Gary I'm sorry I have to ask this silly questions but when I stop the NetworkConnector
via the NetworkConnectorViewMBean what auto-restarts the NetworkConnector?  Perhaps I missed
something in the configuration and that's my problem.  Or, maybe the auto-restart does work
and it's not updating the rmiregistry with the newly start Network connector.  Whatever the
reason, the NetworkConnector does not reappear in JConsole.
> ________________________________
> If you reply to this email, your message will be added to the discussion below:
> To unsubscribe from JMX and NetworkBridge, click here<>.
> NAML<>
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


View raw message