Description of problem:

The following errors occurred several times on the broker while executing bz456272.py test in loop:

2011-04-29 20:02:04 error Execution exception: invalid-argument: anonymous.rhts_mrg-qe-11.lab.eng.brq.redhat.com.9849_2_{(2011, 4, 29, 20, 2, 4, 4, 119, 1)}: confirmed < (251658267+0) but only sent < (46+0) (qpid/SessionState.cpp:154)
2011-04-29 20:02:04 error framing-error: Frame size too small 0 (qpid/framing/AMQFrame.cpp:101)

I also got another, but similar error:

2011-04-29 03:00:39 error framing-error: Framing version unsupported (qpid/framing/AMQFrame.cpp:93)

This was seen on RHEL5.6 and 6.1, architectures: i386, x86_64

Version-Release number of selected component (if applicable):
python-qpid-0.10-1.el5
python-qpid-qmf-0.10-6.el5
qpid-cpp-client-0.10-4.el5
qpid-cpp-client-devel-0.10-4.el5
qpid-cpp-client-devel-docs-0.10-4.el5
qpid-cpp-client-ssl-0.10-4.el5
qpid-cpp-mrg-debuginfo-0.10-4.el5
qpid-cpp-server-0.10-4.el5
qpid-cpp-server-cluster-0.10-4.el5
qpid-cpp-server-devel-0.10-4.el5
qpid-cpp-server-ssl-0.10-4.el5
qpid-cpp-server-store-0.10-4.el5
qpid-cpp-server-xml-0.10-4.el5
qpid-java-client-0.10-4.el5
qpid-java-common-0.10-4.el5
qpid-java-example-0.10-4.el5
qpid-qmf-0.10-6.el5
qpid-qmf-devel-0.10-6.el5
qpid-tools-0.10-4.el5
rh-tests-distribution-MRG-Messaging-qpid_broker_jfail_bz456272-1.5-8
rh-tests-distribution-MRG-Messaging-qpid_common-1.6-56

How reproducible:
very hard ~ 1%
The test was running approximately 2.5 days (1440 loops)

Steps to Reproduce:
This issue reproduction is the same as for BZ701617

1. run client bz456272.py on the broker in the loop
 for more informations please see:
http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/tests/distribution/MRG/Messaging/qpid_broker_jfail_bz456272/

Number of loops can be set with the following variable:
TEST_PARAM_RHTS_TEST_MRG_QPID_BROKER_JFAIL_BZ456272_LOOPS
  
Actual results:
Test result is FAIL. Invalid-argument exception and framing-error error occurs on the broker.

Expected results:
Test result is PASS. No error occurs during the test execution.

Additional info: