Bug 896077

Summary: Qpid python client is unable to receive QMF alerts triggered by java client
Product: Red Hat Enterprise MRG Reporter: Frantisek Reznicek <freznice>
Component: python-qpidAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED NOTABUG QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: DevelopmentCC: esammons, jross, rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-17 08:49:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Testing clients none

Description Frantisek Reznicek 2013-01-16 15:02:02 UTC 
Description of problem:

As part of bug 845223 validation I found that qpid python client is unable to receive QMF alerts triggered by java client.

Testing scenario:
  3 exchangeable clients (c++/python/java) for receiving/triggering client connection QMF alerts.
  Trying to confirm that clientConnect/clientDisconnect/clientConnectFail alerts can be both triggered and received by all above clients.


Observation:
  Java client is able to trigger clientConnect/clientDisconnect/clientConnectFail QMF structured message alert, but just c++ and java receivers are seeing them. Python receiver does not receive/see the alert.


Seen on RHEL 5.9 / 6.4 i386 / x86_64.


Version-Release number of selected component (if applicable):
  python-qpid-0.18-4.el5
  python-qpid-qmf-0.18-13.el5
  qpid-cpp-client-0.18-13.el5
  qpid-cpp-client-devel-0.18-13.el5
  qpid-cpp-client-devel-docs-0.18-13.el5
  qpid-cpp-client-rdma-0.18-13.el5
  qpid-cpp-client-ssl-0.18-13.el5
  qpid-cpp-mrg-debuginfo-0.18-13.el5
  qpid-cpp-server-0.18-13.el5
  qpid-cpp-server-cluster-0.18-13.el5
  qpid-cpp-server-devel-0.18-13.el5
  qpid-cpp-server-rdma-0.18-13.el5
  qpid-cpp-server-ssl-0.18-13.el5
  qpid-cpp-server-store-0.18-13.el5
  qpid-cpp-server-xml-0.18-13.el5
  qpid-java-client-0.18-6.el5
  qpid-java-common-0.18-6.el5
  qpid-java-example-0.18-6.el5
  qpid-jca-0.18-6.el5
  qpid-jca-xarecovery-0.18-6.el5
  qpid-jca-zip-0.18-6.el5
  qpid-qmf-0.18-13.el5
  qpid-qmf-debuginfo-0.18-13.el5
  qpid-qmf-devel-0.18-13.el5
  qpid-tests-0.18-2.el5
  qpid-tools-0.18-7.el5
  rh-qpid-cpp-tests-0.18-13.el5
  ruby-qpid-qmf-0.18-13.el5

How reproducible:
  100%

Steps to Reproduce:
1. service qpidd restart # auth=yes, guest user available
2. start QMF alert receivers (c++/python/java)
./event_receiver $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnect.#'
./event_receiver.py $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnect.#'
./event_receiver.sh $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnect.#'
3. create clientConnect alert from c++ client
./event_receiver $(hostname):5672 "amq.direct" "" -1
4. create clientConnect alert from python client
./event_receiver.py $(hostname):5672 "amq.direct" "" -1
5. create clientConnect alert from java client
./event_receiver.sh $(hostname):5672 "amq.direct" "" -1

All three alert receivers (step 2) should get three QMF clientConnect alerts, one from c++ (step 3), one from python (step 4) and one from java (step5)

Note: event_receiver application is able to receive messages 4th parameter is default or >= 0 or trigger the alert when 4th parameter is -1.

  
Actual results:
Python client is not able to receive QMF alerts caused by java client.

Expected results:
Python client should be able to receive all QMF alerts regardless of client language/lib.

Additional info:

Tested combinations:
  c++ trigger to c++/python/java receiver    functional
  python trigger to c++/python/java receiver functional
  java trigger to c++/java receiver          functional
  java trigger to python receiver            NOT FUNCTIONAL
Comment 1 Frantisek Reznicek 2013-01-16 15:05:17 UTC 
Created attachment 679642 [details]
Testing clients

Detailed testing scenarios:


service qpidd restart


C
./event_receiver $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnect.#'
./event_receiver.py $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnect.#'
./event_receiver.sh $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnect.#'

./event_receiver $(hostname):5672 "amq.direct" "" -1
./event_receiver.py $(hostname):5672 "amq.direct" "" -1
./event_receiver.sh $(hostname):5672 "amq.direct" "" -1


D
./event_receiver $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientDisconnect.#'
./event_receiver.py $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientDisconnect.#'
./event_receiver.sh $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientDisconnect.#'

./event_receiver $(hostname):5672 "amq.direct" "" -1
./event_receiver.py $(hostname):5672 "amq.direct" "" -1
./event_receiver.sh $(hostname):5672 "amq.direct" "" -1


CF
./event_receiver $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnectFail.#'
./event_receiver.py $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnectFail.#'
./event_receiver.sh $(hostname):5672 'qmf.default.topic/agent.ind.event.org_apache_qpid_broker.clientConnectFail.#'

./event_receiver $(hostname):5672 "amq.direct" "{username : guesty, password : guesty, sasl_mechanisms: PLAIN}" -1
./event_receiver.py $(hostname):5672 "amq.direct" "{username : guesty, password : guesty, sasl_mechanisms: PLAIN}" -1
./event_receiver.sh $(hostname):5672 "amq.direct" "{username : guesty, password : guesty, sasl_mechanisms: PLAIN}" -1
Comment 2 Frantisek Reznicek 2013-01-16 20:33:37 UTC 
I'll update the defect tomorrow. I believe I found the reason of above behavior in python client I use for testing. (testing error)

blocker and severity dropped for the moment.
Comment 3 Frantisek Reznicek 2013-01-17 08:49:37 UTC 
It is indeed python client test program issue (testing issue).

Verdict:
Python client is able to receive QMF alerts.

-> CLOSED / NOTABUG