Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 531837 - Java client should set the process ID in the client properties during Connection open
Java client should set the process ID in the client properties during Connect...
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java (Show other bugs)
1.1.7
All Linux
medium Severity medium
: 1.3
: ---
Assigned To: Rajith Attapattu
Jiri Kolar
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-29 11:58 EDT by Rajith Attapattu
Modified: 2010-10-14 12:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the Java client did not set the process ID in the client properties sent via the Connection Open. This information is vital for mapping connections to clients via the management consoles and identifying consumers on a given queue. With this update, the process ID is set.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-10-14 12:15:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0773 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Messaging and Grid Version 1.3 2010-10-14 11:56:44 EDT

  None (edit)
Description Rajith Attapattu 2009-10-29 11:58:42 EDT
Description of problem:
The Java client should set the process ID in the client properties sent via the Connection Open.
This info is vital to map connections to clients via the management consoles.
Also this info is important to identify consumers on a given queue.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
If you turn trace on either client or broker side you should be able to see the connection dialogue.
  
Actual results:
No process ID is set.

Expected results:
Process ID should be set.

Additional info:
Comment 1 Rajith Attapattu 2010-01-12 16:06:50 EST
This is tracked via QPID-2173 in upstream.
A fix for this has been committed at rev 897985 in Qpid trunk.
The qpid.client_process could also be set to something more descriptive as follows using a jvm argument.
-Dqpid.client_process="My Billing App"
Comment 3 Jiri Kolar 2010-09-30 09:25:58 EDT
fixed in qpid-java-client-0.7.946106-10.el5
validated on RHEL5.5/RHEL 4.8  i386 / x86_64  

packages:
# rpm -qa | grep -E '(qpid|openais|rhm)' | sort -u
openais-0.80.6-16.el5_5.7
openais-devel-0.80.6-16.el5_5.7
python-qpid-0.7.946106-14.el5
qpid-cpp-client-0.7.946106-17.el5
qpid-cpp-client-devel-0.7.946106-17.el5
qpid-cpp-client-devel-docs-0.7.946106-17.el5
qpid-cpp-client-ssl-0.7.946106-17.el5
qpid-cpp-mrg-debuginfo-0.7.946106-14.el5
qpid-cpp-server-0.7.946106-17.el5
qpid-cpp-server-cluster-0.7.946106-17.el5
qpid-cpp-server-devel-0.7.946106-17.el5
qpid-cpp-server-ssl-0.7.946106-17.el5
qpid-cpp-server-store-0.7.946106-17.el5
qpid-cpp-server-xml-0.7.946106-17.el5
qpid-java-client-0.7.946106-10.el5
qpid-java-common-0.7.946106-10.el5
qpid-tools-0.7.946106-11.el5
rhm-docs-0.7.946106-5.el5
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-53

->VERIFIED
Comment 4 Martin Prpič 2010-10-10 07:34:14 EDT
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the Java client did not set the process ID in the client properties sent via the Connection Open. This information is vital for mapping connections to clients via the management consoles and identifying consumers on a given queue. With this update, the process ID is set.
Comment 6 errata-xmlrpc 2010-10-14 12:15:02 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0773.html

Note You need to log in before you can comment on or make changes to this bug.