Description of problem:

Qpid qmf c++ client (qmf console) qc_list_objects linked from here:
http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/tests/distribution/MRG/Messaging/qpid_common/clients/c++/

which is used for listing available queues and exchanges occasionly dumps couple of 'Ignoring frame while closing connection' warnings at the client exit. The client still exits with exit code of 0 (i.e. no exception thrown)

The testing scenario:
  There is running broker for couple of days and it is under stress of multiple c++ / python clients upto maximum load (equal to number of cores) of the machine. The issue is happening from really beginning of the test.

Example of qc_list_objects log with warnings:

  [root@mrg-qe-02 qpid_stress_test]# grep -A 30 Exchanges: val_qc_list_objects_27.log
  Exchanges:
  type.direct msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:4138
  MyExchange type.direct msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:0
  amq.direct type.direct durable msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:2
  amq.fanout type.fanout durable msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:0
  amq.match type.headers durable msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:0
  amq.topic type.topic durable msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:0
  qmf.default.direct type.direct msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:1
  qmf.default.topic type.topic msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:1
  qpid.management type.topic msg|byteRx/Drop/Rt:0/0/0|0/0/0 producer_cnt:0 binding_cnt:4
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Bbe; channel=1; {MessageTransferBody: destination=qmfc; accept-mode=1; acquire-mode=0; }]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[be; channel=1; header (79 bytes); properties={{MessageProperties: content-length=96; }{DeliveryProperties: routing-key=console.event.1.0.org.apache.qpid.broker.clientConnect; }}]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Ebe; channel=1; content (96 bytes) AM2e\x00\x00\x00\x00\x16org.apache....].broker
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Bbe; channel=1; {MessageTransferBody: destination=qmfc; accept-mode=1; acquire-mode=0; }]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[be; channel=1; header (75 bytes); properties={{MessageProperties: content-length=121; }{DeliveryProperties: routing-key=console.event.1.0.org.apache.qpid.broker.subscribe; }}]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Ebe; channel=1; content (121 bytes) AM2e\x00\x00\x00\x00\x16org.apache.qpid.broker    ...]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Bbe; channel=1; {MessageTransferBody: destination=qmfc; accept-mode=1; acquire-mode=0; }]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[be; channel=1; header (77 bytes); properties={{MessageProperties: content-length=104; }{DeliveryProperties: routing-key=console.event.1.0.org.apache.qpid.broker.unsubscribe; }}]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Ebe; channel=1; content (104 bytes) AM2e\x00\x00\x00\x00\x16org.apache.qpid.broker
              ...]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Bbe; channel=1; {MessageTransferBody: destination=qmfc; accept-mode=1; acquire-mode=0; }]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[be; channel=1; header (82 bytes); properties={{MessageProperties: content-length=99; }{DeliveryProperties: routing-key=console.event.1.0.org.apache.qpid.broker.clientDisconnect; }}]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Ebe; channel=1; content (99 bytes) AM2e\x00\x00\x00\x00\x16org.apache.qpid.broker\x10...]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Bbe; channel=1; {MessageTransferBody: destination=qmfc; accept-mode=1; acquire-mode=0; }]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[be; channel=1; header (79 bytes); properties={{MessageProperties: content-length=96; }{DeliveryProperties: routing-key=console.event.1.0.org.apache.qpid.broker.clientConnect; }}]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Ebe; channel=1; content (96 bytes) AM2e\x00\x00\x00\x00\x16org.apache....].broker
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Bbe; channel=1; {MessageTransferBody: destination=qmfc; accept-mode=1; acquire-mode=0; }]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[be; channel=1; header (82 bytes); properties={{MessageProperties: content-length=99; }{DeliveryProperties: routing-key=console.event.1.0.org.apache.qpid.broker.clientDisconnect; }}]
  2010-07-26 03:17:52 warning Ignoring frame while closing connection: Frame[Ebe; channel=1; content (99 bytes) AM2e\x00\x00\x00\x00\x16org.apache.qpid.broker\x10...]


Number of messages varies from very few to thousands.


Version-Release number of selected component (if applicable):
The issue was seen on RHEL 5.5 / 4.8 i386 / x86_64 on
packages: 
qmf-0.7.946106-7.el4/5
  and also on latest
qmf-0.7.946106-9.el5

How reproducible:
100%

Steps to Reproduce:
1. run attached test ./runstress.sh
2. watch the log files for above listed message
  
Actual results:
Qpid c++ qmf client reports warning at the exit.

Expected results:
No warnings at Qpid c++ qmf client exit.

Additional info: