[rabbitmq-discuss] Hard limit on API values returned?

[Dustin Doiron]

Hi all,

I believe we've identified a limitation in the values returned by the
/api/connections interface, and was looking to see if anyone else can
confirm this behavior.

It appears that when any field returned in the API request to
/api/connections reaches approximately 4294967296 (2^32), the statistics
counter is dramatically reset, affecting the integrity of counter data in
the next request.

For example, see this selected subset of response for two sequential
requests to /api/connections:

{"recv_oct":4294345813,"recv_cnt":134449509,"send_oct":525608688,"send_cnt":43620989,"send_pend":0,"state":"running","last_blocked_by":"none","last_blocked_age":"infinity","channels":1,"recv_oct_details":{"rate":161293.3401346077,"interval":5002984,"last_event":1377291327321},"send_oct_details":{"rate":2854.2965558154897,"interval":5002984,"last_event":1377291327321},"type":"network","node":"rabbit at localhost
","name":"10.123.123.50:28676 ->
10.123.123.50:5672","address":"10.123.123.50","port":5672,"peer_address":"10.123.123.50","peer_port":28676,"ssl":false,"peer_cert_subject":"","peer_cert_issuer":"","peer_cert_validity":"","auth_mechanism":"PLAIN","ssl_protocol":"","ssl_key_exchange":"","ssl_cipher":"","ssl_hash":"","protocol":"AMQP
0-9-1","user":"webservice","vhost":"webservice","timeout":10,"frame_max":131072,"client_properties":{}}

{"recv_oct":14977,"recv_cnt":134453219,"send_oct":525623280,"send_cnt":43622201,"send_pend":0,"state":"running","last_blocked_by":"none","last_blocked_age":"infinity","channels":1,"recv_oct_details":{"rate":-858689105.5064446,"interval":5001031,"last_event":1377291332322},"send_oct_details":{"rate":2917.798349980234,"interval":5001031,"last_event":1377291332322},"type":"network","node":"rabbit at localhost
","name":"10.123.123.50:28676 ->
10.123.123.50:5672","address":"10.123.123.50","port":5672,"peer_address":"10.123.123.50","peer_port":28676,"ssl":false,"peer_cert_subject":"","peer_cert_issuer":"","peer_cert_validity":"","auth_mechanism":"PLAIN","ssl_protocol":"","ssl_key_exchange":"","ssl_cipher":"","ssl_hash":"","protocol":"AMQP
0-9-1","user":"webservice","vhost":"webservice","timeout":10,"frame_max":131072,"client_properties":{}}

The recv_oct counter reaches approximately 4294967296 between the first and
second requests, causing it to reset for the second request. This also
causes the recv rate to report an incorrect value. We're unsure if this is
a more widespread issue at this time.

Please let me know if additional information is required to reproduce this
behavior.

Thanks,
Dustin Doiron
Weebly.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130826/32009a65/attachment.htm>