[AMQ-642] Add ability to monitor network connections on brokerclient

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0 M4
• Fix Version/s: 4.0 RC2

Environment

All?

• Assignee: James Strachan
• Reporter: elvis P
• Created: 17/Mar/06 11:56
• Updated: 17/Mar/06 15:30
• Resolved: 17/Mar/06 13:26

Description

See: http://forums.activemq.org/posts/list/535.page

In version 3.2.1, broker clients could monitor the state of the connection by listening to a TransportStatusEvent. A listener could be added with this method:

brokerConnection.getTransportChannel().addTransportStatusEventListener(this);

In the 4.0 code this method has changed to:
setTransportListener(eventListener)

This probably means that there can be only one listener to transport-events. I'm guessing that if the client code is set to listen to that event, the failover-protocol will stop functioning.

I think the ability to monitor connection state is a nice feature, so it's too bad that it appears to be removed in the 4.0 code. It think it would only require changing a couple of lines of code to keep it. Interfacewise it would be changing
org.apache.activemq.transport.Transport.setTransportListener()
to
org.apache.activemq.transport.Transport.addTransportListener()

to allow multiple transportlisteners instead of just one.