Try OpenEdge Now
skip to main content
Messaging and ESB
Implementing Messaging : Working with messages : Creating, populating, and accessing messages : Message size limits
 
Message size limits
There is no limit to the ABL message size. However, ABL imposes a 32K limit on each item of a StreamMessage or MapMessage. For more information about text size limits, see XML code page encoding .
SonicMQ does not have a hard-coded maximum message size; the largest tested message is 1MB.
When using very large messages (exceeding 1MB), you might need to modify the JVM's memory limit values, specified in the jvmArgs property of the AdminServerPlugins.properties file. For example, if the OpenEdge Adapter for SonicMQ fails with an OutofMemory error in the log, you should modify the arguments for the sizes of the memory heap (-mx) and the stack (-ss). The following sample entry specifies 40MB for the memory heap and 8MB for the stack:
jvmArgs= –Xmx40m –Xss8m
Note: You can use the mergeprop utility installed with OpenEdge to manually edit the AdminServerPlugins.properties file. For information on using mergeprop, see OpenEdge Getting Started: Installation and Configuration.