Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 531837

Summary:	Java client should set the process ID in the client properties during Connection open
Product:	Red Hat Enterprise MRG	Reporter:	Rajith Attapattu <rattapat+nobody>
Component:	qpid-java	Assignee:	Rajith Attapattu <rattapat+nobody>
Status:	CLOSED ERRATA	QA Contact:	Jiri Kolar <jkolar>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.1.7	CC:	jkolar
Target Milestone:	1.3
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
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 16:15:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rajith Attapattu 2009-10-29 15:58:42 UTC

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 21:06:50 UTC

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 13:25:58 UTC

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 11:34:14 UTC

    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 16:15:02 UTC

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