Add ability to monitor network connections on brokerclient
----------------------------------------------------------
Key: AMQ-642
URL: http://jira.activemq.org/jira//browse/AMQ-642
Project: ActiveMQ
Type: Improvement
Versions: 4.0 M4
Environment: All?
Reporter: LarsE
Fix For: 4.0 M5
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
