Hi, The current schema (well, current ... Qpid 0.10 / MRG 2.0) for a queue seems to handle byteDepth only as uint32:
qpid: schema queue Object Class: Table Class: org.apache.qpid.broker:queue:_data(bfd4d378-c6e6-efb6-f0d0-963252cedfaa) Element Type Access Unit Notes Description ======================================================================================================= vhostRef reference ReadCreate index name short-string ReadCreate index durable boolean ReadCreate autoDelete boolean ReadCreate exclusive boolean ReadCreate arguments field-table ReadOnly Arguments supplied in queue.declare altExchange reference ReadOnly optional msgTotalEnqueues uint64 msgTotalDequeues uint64 msgTxnEnqueues uint64 msgTxnDequeues uint64 msgPersistEnqueues uint64 msgPersistDequeues uint64 msgDepth uint32 byteDepth uint32 byteTotalEnqueues uint64 byteTotalDequeues uint64 byteTxnEnqueues uint64 byteTxnDequeues uint64 bytePersistEnqueues uint64 bytePersistDequeues uint64 consumerCount uint32 consumerCountHigh uint32 consumerCountLow uint32 bindingCount uint32 bindingCountHigh uint32 bindingCountLow uint32 unackedMessages uint32 unackedMessagesHigh uint32 unackedMessagesLow uint32 messageLatencySamples delta-time messageLatencyMin delta-time messageLatencyMax delta-time messageLatencyAverage delta-time flowStopped boolean flowStoppedCount uint32 Given the possibilities of Qpid, the uint32 seems to be a limitation. I already got into situations, where uint32 is not sufficient and one has to use the enqueue and dequeue statistics to calculate the actual byte depth: msgDepth 30000155 byteDepth 3421958148 byteTotalEnqueues 24896794628 byteTotalDequeues 0 I entered a JIRA QPID-3465 for this problem. Regards Jakub --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscr...@qpid.apache.org