BEA WebLogic Server 9.1 Domain Configuration Schema Reference

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 (in bytes) that this JMS server can use to store message bodies before it writes them to disk. When the JMS server writes the message bodies to disk, it clears them from memory.

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.

Paging is always supported.

Privileges: Read/Write

Default Value: -1

Minimum value: -1

Maximum value: 9223372036854775807

MBean Attribute: JMSServerMBean.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
BEA WebLogic Server 9.1 Domain Configuration Schema Reference

Version: 9.1