There is no easy answer, the a new bridge is created after each
failure, so there is no resume, just a new start.
The corresponding mbeans come and go as the bridges start and
disappear so JMX could give you a handle to active bridges and
possibly a notification on mbean registration.
Another
Gary, thanks for the answer. I'll see what I can figure out.
Brett
On Wed, Dec 8, 2010 at 10:19 PM, Gary Tully gary.tu...@gmail.com wrote:
There is no easy answer, the a new bridge is created after each
failure, so there is no resume, just a new start.
The corresponding mbeans come and go
I have a dynamic network of brokers (created programmatically). And I
have a need for the hub broker to know about the comings and goings
of the spoke brokers' connections.
For example, take this topology:
Broker A Broker B
Broker A is the hub, and initiates a bridge to Broker B
