You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "LarsE (JIRA)" <ji...@activemq.org> on 2006/03/17 12:58:25 UTC
[jira] Created: (AMQ-642) Add ability to monitor network
connections on brokerclient
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
[jira] Commented: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=comments#action_35799 ]
james strachan commented on AMQ-642:
------------------------------------
Great - yes thats right. Changes in subversion get included in the nightly build; so you should be able to use tomorrows SNAPSHOT distro
> 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
> Assignee: james strachan
> 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
[jira] Commented: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=comments#action_35793 ]
james strachan commented on AMQ-642:
------------------------------------
:) I guess you can be a beta tester of it to check it works as advertised. (Given the simplicity of the patch I'm pretty sure its fine though :)
> 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
> Assignee: james strachan
> 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
[jira] Resolved: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=all ]
james strachan resolved AMQ-642:
--------------------------------
Resolution: Fixed
I've added addTransportListener()/removeTransportListener() methods to ActiveMQConnection which should do what you need :)
> 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
> Assignee: james strachan
> 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
[jira] Commented: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "LarsE (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=comments#action_35798 ]
LarsE commented on AMQ-642:
---------------------------
I'd like to test it, in fact I was looking for a version with your fix in it right now. I'll have to wait for the SNAPSHOT for 17-Mar-2006 to get it as binary, isn't that right?
> 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
> Assignee: james strachan
> 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
[jira] Commented: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "LarsE (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=comments#action_35792 ]
LarsE commented on AMQ-642:
---------------------------
That is very cool :-) And fast!
> 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
> Assignee: james strachan
> 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
[jira] Assigned: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "james strachan (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=all ]
james strachan reassigned AMQ-642:
----------------------------------
Assign To: james strachan
> 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
> Assignee: james strachan
> 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
[jira] Commented: (AMQ-642) Add ability to monitor network
connections on brokerclient
Posted by "LarsE (JIRA)" <ji...@activemq.org>.
[ http://jira.activemq.org/jira//browse/AMQ-642?page=comments#action_35800 ]
LarsE commented on AMQ-642:
---------------------------
:-) Will probably get around to test it monday morning.
> 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
> Assignee: james strachan
> 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