I am working with Weblogic 10.3. I created a custom domain and inside thim i created a new server and machine. I am trying to do deployment a standard EMC web application (Documentum Webtop) and I get this error "java.lang.OutOfMemoryError: PermGen space". I modified this parameters in my enviroment at this config files because i use Node Manager:
@REM set MEM_ARGS=-Xms256m -Xmx512m
set MEM_ARGS=-Xms1024m -Xmx1024m
@REM set MEM_MAX_PERM_SIZE=-XX:MaxPermSize=128m
After this change, i get de same error.
@rem set MEM_ARGS=-Xms32m -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning
set MEM_ARGS=-Xms32m -Xmx200m -XX:MaxPermSize=256m -XX:+UseSpinning
After this change, i get de same error too.
Could anybody tell me what is wrong and what script should I change?
How are u starting your Server using NodeManager or using StartScript? I think that the changes are not being picked up by your Managed Server...Have u confirmed it by looking at the managed Server Logs or STDOUT ...what was the Heap & PerSize there while starting in STDOUT.?
If you are starting your Managed Server using NodeManager then First of all try the following options as well..
Login to AdminConsole-->Environments---.Servers--->YourManagedServer--->Configuration (TAB)--->ServerStart (SubTab)---> Arguments:(TextArea) -Xms1024m -Xmx1024m -XX:MaxPermSize=256m
Specify the Heap & MaxPermSize setting here.. in the TextArea ...Then start your Server.
If option-1 doesn't work then.... Option-2). If above also didn't work then please try to add the following 2 entry in the "nodemanager.properties" file and in startWebLogic.cmd please add the JAVA_OPTION=-Xms1024m -Xmx1024m -XX:MaxPermSize=256m
I choose the option 1 and work fine. This is my start secuence:
1. Start node manager script (starNodeManager.cmd).
2. Start admin server for my domain (startWeblogic.cmd).
3. Open admin server console and add this arguments.
4. Start my custom server using admin server console.
In many production scenario i have seen that we should set the MaxPermSize at least 256M.
Second thing We need to look at the Server Stdout/Server log first few line that whatever values we are setting for PermSize is getting reflected there or not...many cases whatever changes we made in our startScripts are not in appropriate place so they are not reflected.
Are you starting your Server Using AdminConsole...means with the Help of NodeManager...?
Or Are u starting your Servers using script like "startManagedWebLogic.sh" ?
Jay SenSharma http://middlewaremagic.com/weblogic/?p=4464 (Middleware magic Is Here)*
I did my installation on Windows Server and i used node manager. I modify setDomainEnv.cmd and commEnv.cmd but this changes doesnt i solved my problem restore the original files (setDomainEnv.cmd, commEnv.cmd) and i used administration console to increase this parameters values in my custom server. At the correct post, jay indicate 2 options to solved the problem and i follow the first one and my enviroment work fine.
Thanks Jay. We have changed startWebLogic.sh the way you suggested. But the change is not reflecting when we start the server.
We can see the same set of lines when we start the server-
Starting WLS with line:
/usr/jdk/instances/jdk1.6.0/bin/java -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -XX:MaxPermSize=160m -Dweblogic.Name=AdminServer-8001 -Djava.security.policy=/export/home/eaiapppr/bea_home/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
<Mar 5, 2010 4:40:39 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 16.0-b13 from Sun Microsystems Inc.>
As of now we are retaining the changes within setDomainEnv.sh, as we have only Admin server within that domain.In setDomainEnv.sh there is a line which is setting maxPermSize as 160m.