[
https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676284#action_12676284
]
Ted Ross commented on QPID-1676:
--------------------------------
More details on the fields:
qpid.client_process:
This can be either the process name (i.e. from the linux/unix 'ps' command) or
it can be the basename from argv[0]. In other words, if argv[0] is
"/usr/bin/qpid-config", the content of the field will be "qpid-config".
The latter is preferable for clients written in Python and Ruby because the
process name tends to be simply "python" or similar.
qpid.client_pid and qpid.client_ppid:
These are derived from the posix getpid and getppid, or equivalent.
> Management access to client process name and PID
> ------------------------------------------------
>
> Key: QPID-1676
> URL: https://issues.apache.org/jira/browse/QPID-1676
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Minor
> Fix For: M5
>
>
> When viewing connection information in the broker, it is useful to be able to
> access the process name and PID of the client process (on the remote system).
> This can be used by an administrator to stop a process that is causing
> problems on the AMQP network.
> I propose including (optionally) this information in the "client-properties"
> field of the "start-ok" message using the following keys:
> qpid.client_process (process name)
> qpid.client_pid (process ID)
> qpid.client_ppid (parent process ID)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
