Description of problem: Having an AMQP 1.0 client, its QMF connection statistics listed below are not updated: framesFromClient framesToClient bytesFromClient bytesToClient Version-Release number of selected component (if applicable): qpid-cpp-server-0.22-44 How reproducible: 100% Steps to Reproduce: 1. in 1st terminal, run qpid-tool 2. in some other terminal, run: qpid-send -a "q; {create:always}" -m10 --content-size=10 --connection-options "{protocol:amqp1.0}" qpid-receive -a "q; {create:always}" -m10 --connection-options "{protocol:amqp1.0}" 3. in qpid-tool. "list connection" and then "show X" where X is the ID of either of two deleted connections Actual results: All above mentioned statistics are zero. Expected results: Relevant stats should be updated (at least *FromClient for qpid-send and *ToClient for qpid-receive connection) Additional info: It works well for 0-10, just 1.0 does not call "cStats->framesFromClient += 1;" or so.
The bytes to/from the client are easy enough to add. The frames are a little harder since it is actually the proton library that decodes those and doesn't expose that information directly. It could certainly be done there as well, but I wonder how useful those stats are in practice. If you have message and byte counts, would that be sufficient?
(In reply to Gordon Sim from comment #1) > The bytes to/from the client are easy enough to add. The frames are a little > harder since it is actually the proton library that decodes those and > doesn't expose that information directly. It could certainly be done there > as well, but I wonder how useful those stats are in practice. If you have > message and byte counts, would that be sufficient? I think so; frame counts is in my opinion little bit artificial counter and I am not aware of an user interested in those values. Maybe just worth mentioning in management-schema.xml this limitation.
(In reply to Gordon Sim from comment #1) > The bytes to/from the client are easy enough to add. The frames are a little > harder since it is actually the proton library that decodes those and > doesn't expose that information directly. It could certainly be done there > as well, but I wonder how useful those stats are in practice. If you have > message and byte counts, would that be sufficient? Yes, I think so. As I recall, we used frames because it was very difficult to count messages at the connection level. It was always preferable to count messages.
(In reply to Gordon Sim from comment #1) > The bytes to/from the client are easy enough to add. The frames are a little > harder since it is actually the proton library that decodes those and > doesn't expose that information directly. Actually that is no longer true. Frame counts in both directions are available for the transport so the fix should be simple.