[
https://issues.apache.org/jira/browse/QPID-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Moravec updated QPID-4174:
--------------------------------
Component/s: (was: Java Client)
Qpid Managment Framework
Description:
I suggest enhancing values populated in 3 events relevant for client
(dis)connection:
clientConnect
clientConnectFail
clientDisconnect
For these events, I suggest adding values:
remoteParentPid
remotePid
remoteProcessName
That is useful for various reasons:
1) To have better information who just disconnected or failed to connect (i.e.
better monitoring allowing to easily identify the process that is e.g. failing
to connect repeatedly)
2) To allow client processes (listening for the events) to easily know the
disconnect event is relevant to itself by comparing its PID with remotePid.
I am attaching a patch for it.
was:
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.
Summary: QMF events for (dis)connecting a client to have few more
parameters (was: Allow getting information about established TCP connection in
Java client)
> QMF events for (dis)connecting a client to have few more parameters
> -------------------------------------------------------------------
>
> Key: QPID-4174
> URL: https://issues.apache.org/jira/browse/QPID-4174
> Project: Qpid
> Issue Type: Improvement
> Components: Qpid Managment Framework
> Affects Versions: 0.14
> Reporter: Pavel Moravec
> Priority: Minor
> Labels: patch
>
> I suggest enhancing values populated in 3 events relevant for client
> (dis)connection:
> clientConnect
> clientConnectFail
> clientDisconnect
> For these events, I suggest adding values:
> remoteParentPid
> remotePid
> remoteProcessName
> That is useful for various reasons:
> 1) To have better information who just disconnected or failed to connect
> (i.e. better monitoring allowing to easily identify the process that is e.g.
> failing to connect repeatedly)
> 2) To allow client processes (listening for the events) to easily know the
> disconnect event is relevant to itself by comparing its PID with remotePid.
> I am attaching a patch for it.
--
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]
