You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <ji...@apache.org> on 2012/07/30 19:41:34 UTC
[jira] [Commented] (QPID-4174) Allow getting information about
established TCP connection in Java client
[ https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425039#comment-13425039 ]
Rajith Attapattu commented on QPID-4174:
----------------------------------------
I'm not too keen about this approach.
QMF has more details (ex process name, pid etc) at it's disposal. A monitoring application could use this already available information to correlate connections to events.
If QMF doesn't send this information in events already, then it should probably do it.
At the moment qpid.client_process is set as a jvm argument. This could be easily included on a per connection basis as well.
That way you could give more meaningful identifier for each connection and then use them in monitoring applications.
> Allow getting information about established TCP connection in Java client
> -------------------------------------------------------------------------
>
> Key: QPID-4174
> URL: https://issues.apache.org/jira/browse/QPID-4174
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.14
> Reporter: Pavel Moravec
> Priority: Minor
> Labels: patch
> Attachments: 0001_QPID-4174_AllowTCPconn-info.patch
>
>
> Java client does not offer a method to print out active TCP connection (like string "127.0.0.1:12345->127.0.0.1:5672"). Pure JMS API does not offer so at all, checking sources of Java client shows the underlying TCP socket is kept in a private member of a class that does not offer a (readonly) access to the member.
> The enhancement is meaningful for management purposes to detect connectivity. If the Java client listens for QMF updates from the qpid broker, it get events like "127.0.0.1:12345->127.0.0.1:5672 disconnected". But currently it can not match the event to its local connection(s) as it doesn't know them.
> I am attaching a simple patch file such that AMQConnection class is extended by getSocketString() method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org