Technical data

17 Managing JMS
17-30 Administration Guide
Note: If server paging is enabled, and destination-level paging is disabled for a given
destination, than messages on the destination can still be paged if server
paging is triggered. However, when destination-level paging is disabled for a
given destination, then the destination’s high thresholds will not force the
destination to page out messages when they are exceeded.
Paging Threshold Attributes
Table 17-4 briefly describes the bytes and messages paging thresholds available with
JMS servers, templates, and destinations. For detailed information about other JMS
server, template, and destination attributes, and the valid and default values for them,
see “JMS Servers,” “JMS Destinations,” and “JMS Templates” in the Administration
Console Online Help.
The thresholds are defined for servers, templates, and destinations as follows:
n If either bytes high/low threshold value is not defined (or is defined as -1), then
the number of bytes is not used to determine when and what to page.
n If either messages high/low threshold value is not defined (or is defined as -1),
then the number of messages is not used to determine when and what to page.
n A server or template/destination must have the Bytes/Messages Paging Enabled
attribute set to True in order for paging to take place. If the thresholds are set,
but paging is not enabled, messages are still logged on the server indicating
threshold conditions.
Table 17-4 Paging Threshold Attributes
Attribute Description
Bytes Threshold High Start paging when the number of bytes exceeds this
threshold.
Bytes Threshold Low Stop paging when the number of bytes falls back
below this threshold.
Messages Threshold High Start paging when the number of messages exceeds
this threshold.
Messages Threshold Low Stop paging when the number of messages falls back
below this threshold.