Why is the value of "pendingMessageSizeUsage" for a queue in the Hawk display "0" although there are pending messages on the queue?

Why is the value of "pendingMessageSizeUsage" for a queue in the Hawk display "0" although there are pending messages on the queue?

book

Article ID: KB0094497

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
Description:
=========
The parameter "pendingMessageSizeUsage" for a queue in the Hawk display is defined by the JMS controller microagent as “PendingMessageSize()/maxBytes”.  If the maxBytes property of the queue is "0" then "pendingMessageSizeUsage" will be "0" as well.  
    
"maxbytes" and "maxmsgs" are destination properties.  They can be defined for both topics and queues. For queues, maxbytes defines the maximum size (in bytes) that the queue can store summed over all messages in the queue. Should this limit be exceeded, messages will be rejected by the server and the message producer send calls will return an error (see also overflowPolicy).

For more informations regarding maxbytes, refer to the EMS User's Guide -> Destinations -> Destination Properties.  

Platforms:
========
All

Keywords:
========
maxbytes pendingMessageSizeUsage hawk display

Issue/Introduction

Why is the value of "pendingMessageSizeUsage" for a queue in the Hawk display "0" although there are pending messages on the queue?