BEA WebLogic Server 9.0 Domain Configuration Schema Reference

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

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

Documentation
The maximum number of bytes allowed in individual messages on
 this SAF agent.


  - 


The message size includes the message body, any user-defined
 properties, and the user-defined JMS header fields:
 JMSCorrelationID and JMSType.



  - 


Producers sending messages that exceed the configured maximum
 message size for the SAF agent will receive a
 ResourceAllocationException.



  - 


The maximum message size is only enforced for the initial
 production of a message. Messages that are redirected to an error
 destination or forwarded to a member of a distributed destination
 are not checked for size. For instance, if a destination and its
 corresponding error destination are configured with a maximum
 message size of 128K bytes and 64K bytes, respectively, a message
 of 96K bytes could be redirected to the error destination (even
 though it exceeds the 64K byte maximum), but a producer could not
 directly send the 96K byte message to the error destination.



  - 


Applies only to agents with sending capability.



  - 


Updating MaximumMessageSize affects only incoming
 messages; stored messages are not affected.




 


 Legal Min: 0


 Default: java.lang.Integer.MAX_VALUE
Properties
This component is not nillable.

Model
<maximum-message-size>

</maximum-message-size>

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

BEA WebLogic Server 9.0 Domain Configuration Schema Reference

Copyright 2005 BEA Systems Inc. Complete WebLogic Server Documentation