[
https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755631#action_12755631
]
Ted Ross commented on QPID-1676:
--------------------------------
The client_ppid is simply reported as a way to help identify the process
running as the client. If parent-process is not supported on a particular
platform, there is no harm in simply setting the value to zero.
I'll attach a patch with a possible fix.
-Ted
> 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: 0.5
>
>
> 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]
