with a partially failed duplex bridge, to get it recreated, you need to restart the network connector, so that the initiator again starts to create the duplex bridge. It is not possible to just start the duplex responder end as all of the info it needs from the initiator needs to be resent.
Maybe the inactivity monitor is the answer here, it will detect the remote connection loss and teardown and recreate the bridge. For JMX, just use the NetworkConnectorViewMBean to do the restart. stop/restart on the network connector and it will recreate all of the bridges. Or just find the single bridge mbean and stop it. The network connector will auto recreate that. what version are you on? On 20 June 2012 14:45, billy <billy.buzz...@bnsflogistics.com> wrote: > Thanks for the information, but sorry to hear that the possibilities are > limited at this time. The actual problem I was trying to solve has to do > with a partially failed duplex network bridge. The non-creating side of a > duplex network bridge is dropping for some unknown reason while the creating > side is still up and running. I can easily use JMX to detect the problem, > but I needed a way to recreate the bridge as soon as the drop was detected. > I'm using a spoke-and-hub topology, one of the spokes is an old WindowsXP > Pro machine and all I wanted to do was restart its networkbridge when I > detect it going down. > > Is it possible to create a SpringBean with JMX access that could > recreate/start the networkbridge? If yes, where's a good place to start > looking in the code to figure out how networkbridges are created from the > ActiveMQ.xml file? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/JMX-and-NetworkBridge-tp4653357p4653391.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://fusesource.com http://blog.garytully.com
