Kbase 34067: How to limit the memory consumption of Java within SonicMQ
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Solution ID: P4067
GOAL:
How to limit the memory consumption of Java within SonicMQ
FACT(s) (Environment):
SonicMQ 4.x
FIX:
-- Java
The -mx ( jre 1.1.x ) or -Xmx ( jre 1.2x or jre 1.3.x ) startup parameters limit the maximum memory (heap size) consumption for the Java process. But this applies only if more than that amount of memory is free on the machine. Neither of these parameters will set a pre-allocated amount of memory for the Java process. Also, if memory happens to be allocated to another active process and there is less free memory available at runtime, it will not help to increase the -mx (or -Xmx) parameter value.
If you need to pre-allocate more memory, then higher values for the -ms ( jre 1.1.x) or -Xms ( jre 1.2x or jre 1.3.x ) startup parameter will help. Likewise, this is true only if that amount of memory is available at startup of the Java application.
-- SonicMQ broker
For the SonicMQ broker the maximum memory used depends on how much and how many queues are filled. By default, every queue is limited to 1MB in memory allocation, but that setting is changeable for each queue individually. Tools to change the settings are the SonicMQ Explorer Tool and the Admin shell. It is also possible to change the setting programmatically using the Admin API.