If a federation route is created that attempts to bind to a nonexistent exchange, there is no error indication. Furthermore, when this route is later deleted, the two brokers attached by the link infinitely send session.detached messages to each other.
The infinite detached loop has been fixed. The lack of error indication is still a problem.
Simple solution (good enough for GA?): Routes that reference exchanges that do not exist will not function (as you might expect). In fact, the session created for them shall be detached upon bind failure. Other routes on the same link will function normally. If the referenced exchange is subsequently created, the route will become operational only after the link is bounced (i.e. disconnected and re-established). There is no user-observable indication that the route is not working.
Ted, what's the status of this one?
(In reply to comment #3) > Ted, what's the status of this one? The behavior is still as described in Commend 2.