[
https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-4174:
--------------------------------
Attachment: 0001_QPID-4174_AllowTCPconn-info.patch
Proposed enhancement patch.
> 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
