You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <qp...@incubator.apache.org> on 2009/02/23 19:04:02 UTC
[jira] Created: (QPID-1676) Management access to client process
name and PID
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:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-1676) Management access to client process
name and PID
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross resolved QPID-1676.
----------------------------
Resolution: Fixed
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-1676) Management access to client process
name and PID
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Commented: (QPID-1676) Management access to client process
name and PID
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756106#action_12756106 ]
Steve Huston commented on QPID-1676:
------------------------------------
Excellent - works great, Ted - thanks!
> 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
>
> Attachments: python.patch
>
>
> 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
[jira] Issue Comment Edited: (QPID-1676) Management access to
client process name and PID
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756106#action_12756106 ]
Steve Huston edited comment on QPID-1676 at 9/16/09 10:02 AM:
--------------------------------------------------------------
Excellent - works great, Ted - thanks! Patch applied in trunk r815884
was (Author: shuston):
Excellent - works great, Ted - thanks!
> 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
>
> Attachments: python.patch
>
>
> 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
[jira] Commented: (QPID-1676) Management access to client process
name and PID
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-1676) Management access to client process
name and PID
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1676) Management access to client process
name and PID
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross updated QPID-1676:
---------------------------
Attachment: python.patch
Patch to handle environments where "os.getppid()" is not defined.
> 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
>
> Attachments: python.patch
>
>
> 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