2004.9.17 Learn a lot in the performance test process today, plus the accumulation of the previous period, the record is as follows:
One: WebLogic configuration problem: Due to WebLogic configuration issues, our test has failed. The reason is that there is too little memory allocated for WebLogic. Increase the memory allocation by modifying the comMM / bin / commenv.cmd file. Modified part as follows :: beaif "% PRODUCTION_MODE%" == "true" goto bea_prod_modeset JAVA_VM = -jrockitset MEM_ARGS = -Xms768m -Xmx1024mset JAVA_OPTIONS =% JAVA_OPTIONS% -Xverify: nonegoto continue: bea_prod_modeset JAVA_VM = -jrockitset MEM_ARGS = -Xms768m - XMX1024M // It turned out to be 128M ~ 256M, too small, data too large GOTO Continue
The result is modified, there is no effect. Still there is a failure. Discover, it turns out that there is another configuration information below: BEA as follows:
: Sunif "% PRODUCTION_MODE%" == "true" goto sun_prod_modeset JAVA_VM = -clientset MEM_ARGS = -Xms768m -Xmx1024m -XX: MaxPermSize = 256mset JAVA_OPTIONS =% JAVA_OPTIONS% -Xverify: nonegoto continue: sun_prod_modeset JAVA_VM = -serverset MEM_ARGS = -Xms768m -XMX1024M -XX: maxpermsize = 256mgoto continue will modify the memory allocation here. The reason is that the above code is set for the BEA's own JVM, below is set for Sun. WebLogic defaults to Sun, so there is a problem.
