[
https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425572#comment-13425572
]
Pavel Moravec commented on QPID-4174:
-------------------------------------
I agree enriching the connect / disconnect QMF event by more fields (i.e.
remotePid or remoteProcessName) will be better approach - I will discuss it
with Ted Ross. FYI, connect / disconnect QMF event is of form:
{_schema_id:{_class_name:clientConnect,
_hash:f59fe634-9c51-cfce-b3be-63bf063a0ac2,
_package_name:org.apache.qpid.broker, _type:_event}, _severity:6,
_timestamp:1343713841536668379, _values:{rhost:[::1]:5672-[::1]:44657,
user:anonymous}}
While compared to "get connections" QMF query returning much more information:
{_create_ts:1343713833158589940, _delete_ts:0, _object_id:{_agent_epoch:9,
_object_name:org.apache.qpid.broker:connection:[::1]:5672-[::1]:44656},
_schema_id:{_class_name:connection, _hash:09a39a61-d09a-6a80-1f85-670a97557a46,
_package_name:org.apache.qpid.broker, _type:_data},
_update_ts:1343713833207393722, _values:{SystemConnection:False,
address:[::1]:5672-[::1]:44656, authIdentity:anonymous, bytesFromClient:1157,
bytesToClient:312, closing:False, federationLink:False, framesFromClient:18,
framesToClient:10, incoming:True, msgsFromClient:1, msgsToClient:0,
remoteParentPid:28802, remotePid:28819, remoteProcessName:watch-connectio,
saslMechanism:, saslSsf:0, shadow:False, userProxyAuth:False,
vhostRef:{_object_name:org.apache.qpid.broker:vhost:org.apache.qpid.broker:broker:amqp-broker,/}}}
> 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: [email protected]
For additional commands, e-mail: [email protected]
