BEA WebLogic Server 9.0 Domain Configuration Schema Reference

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

Super Types
{http://www.w3.org/2001/XMLSchema}long
|
+--{http://www.bea.com/ns/weblogic/90/domain} (restriction)

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.
Properties
This component is not nillable.

Model
<message-buffer-size>

</message-buffer-size>

Source
<xs:element minOccurs="0" name="message-buffer-size" nillable="false">
<xs:simpleType>
<xs:restriction base="xs:long">
<xs:minInclusive value="-1"/>
</xs:restriction>
</xs:simpleType>
</xs:element>

BEA WebLogic Server 9.0 Domain Configuration Schema Reference

Copyright 2005 BEA Systems Inc. Complete WebLogic Server Documentation