You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Steve Huston (JIRA)" <qp...@incubator.apache.org> on 2009/09/15 20:28:57 UTC
[jira] Commented: (QPID-1676) Management access to client process
name and PID
[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755626#action_12755626 ]
Steve Huston commented on QPID-1676:
------------------------------------
Is the parent pid (client_ppid) used anywhere? The call to get this information (os.getppid) is not available on Windows. This prevents the Python qpid tools from running. If I comment out the getppid call, things seem to work - at least a few sample runs of qpid-config and qpid-tool seem to be ok.
> 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:dev-subscribe@qpid.apache.org