-XMS cannot exceed 25% of the physical memory
-Xmx cannot exceed 1.8 GB (32-bit CPU)
When I use jrockit (webogic8.1sp2), no more than 1.6 GB-XMS can be set to 512 MB.
An error is reported when startup is too large. What about 3G server memory?
Today, I learned a lot in the performance testing process. With the accumulation of some time ago, the special record is as follows:
I. WebLogic configuration problems:
Due to WebLogic configuration problems, our test fails. The reason is that there is too little memory allocated for weblogic. Increase the memory allocation by modifying the commom \ bin \ commenv. CMD file.
The modified part is as follows:
: BEA
If "% production_mode %" = "true" Goto bea_prod_mode
Set java_vm =-jrockit
Set mem_args =-xms768m-xmx1024m
Set java_options = % java_options %-xverify: None
Goto continue
: Bea_prod_mode
Set java_vm =-jrockit
Set mem_args =-xms768m-xmx1024m // originally M ~ 256 m, too small, too big data
Goto continue
The modification results have no effect. There are still failures.
It turns out that there is still a piece of configuration information below: BEA:
: Sun
If "% production_mode %" = "true" Goto sun_prod_mode
Set java_vm =-Client
Set mem_args =-xms768m-xmx1024m-XX: maxpermsize = 256 m
Set java_options = % java_options %-xverify: None
Goto continue
: Sun_prod_mode
Set java_vm =-Server
Set mem_args =-xms768m-xmx1024m-XX: maxpermsize = 256 m
Goto continue
Modify the memory allocation.
The reason is that the first paragraphCodeIt is set for Bea's own JVM, and the following is the setting for sun. WebLogic is Sun by default, so something went wrong.
------------------------- Another note :------------------------------
Startweblogic. cmd
The file calls commenv. cmd,
Set the memory size in this file to take effect.
Call "% wl_home % \ common \ bin \ commenv. cmd"
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/chasnoly/archive/2009/02/16/3894919.aspx