For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 1 voice, and was last updated 21 years, 7 months ago by
.
-
Posts
-
Hi Riyad and Scott,
no matter how I try, WLS still does NOT take the -Xmx512m parameter from the optional Java VM parameters.
I tried switching to JDK1.4.1_05 under the c:\bea\jdk141_05,
tried adding the -Xms256m besides -Xmx512m as Scott suggested, still the started Weblogic instance throws OutOfMemoryError when reaching 256 megabyte memory usage (verified by tracking the process with Task Manager).I am using Windows XP, ME 3.7.2, Weblogic 8.1 SP2, tried Sun JDK 1.4.1_05 and 1.4.2_04.
I need to get this working very urgently since I have to track down an error, which I can find only by debugging.
If you have this working, then please post the appropriate configuration screenshots on the forum or send it to me in an email (no BMP though, our mailserver drops BMP attachments).
That it is really working can be easily tested by specifying the -Xms256m parameter, that should make the WLS JVM started with 256meg memory usage in Task Manager, and that is not behaving so in my system.
Thanks in advance,
Robert
@robvarga wrote:
Hi Riyad and Scott,
no matter how I try, WLS still does NOT take the -Xmx512m parameter from the optional Java VM parameters.
I tried switching to JDK1.4.1_05 under the c:\bea\jdk141_05,
tried adding the -Xms256m besides -Xmx512m as Scott suggested, still the started Weblogic instance throws OutOfMemoryError when reaching 256 megabyte memory usage (verified by tracking the process with Task Manager).I am using Windows XP, ME 3.7.2, Weblogic 8.1 SP2, tried Sun JDK 1.4.1_05 and 1.4.2_04.
I need to get this working very urgently since I have to track down an error, which I can find only by debugging.
If you have this working, then please post the appropriate configuration screenshots on the forum or send it to me in an email (no BMP though, our mailserver drops BMP attachments).
That it is really working can be easily tested by specifying the -Xms256m parameter, that should make the WLS JVM started with 256meg memory usage in Task Manager, and that is not behaving so in my system.
Thanks in advance,
Robert
OK, problem solved. I guess the problem was not the heap size, but the perm size. If I passed in all memory-related parameters that are added by the setDomainEnv.cmd (-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m) when run from command line, it managed to start up properly.
Regards,
Robert Varga
