http://www.bea.com/ns/weblogic/90/domain
element message-buffer-size

Model

<message-buffer-size>annonymous type derived from long</message-buffer-size>

Disallowed substitutions (block)

none (extensions, restrictions and substitutions are allowed)

Substitution group exclusion (final)

none (extensions and restrictions are allowed)

Usage

Documentation

The amount of memory used to store message bodies in memory before they are paged out to disk.

• A value of -1 (the default) specifies that the server will automatically determine a size based on the maximum heap size of the JVM. This default will be set to either one-third the maximum heap size, or 512 megabytes, whichever is larger.

• The larger the buffer, the more memory JMS will consume when many messages are waiting on queues or topics. Once the buffer is surpassed, JMS may write message bodies to the directory specified by PagingDirectory in an effort to reduce memory usage below this buffer.

• Surpassing the buffer size does not stop the JMS server from accepting new messages. It is still possible to run out of memory if messages are arriving faster than they can be written to disk. Users with high messaging loads who wish to support the highest possible availability should consider setting a quota or setting a threshold and enabling flow control.

• Applies only to agents with sending capability.

• Paging is always supported.

• Updating the memory size resets the message count so that only requests arriving after the update are charged against the new memory size.

Privileges: Read/Write

Default Value: -1

Minimum value: -1

MBean Attribute: SAFAgentMBean.MessageBufferSize

Fundamental Facets

equality, numeric, bounded, totaly ordered, countable infinite value space

White Space Processing

collapse

Pattern Facet

[\-+]?[0-9]+

Digits Facets

fraction digits: 0