java.lang.OutOfMemoryError: PermGen space in Weblogic startup

-
PermGen or Permanent Generation space is a part of Heap where it stores the Class definitions.By default JVM will take the value as 32m,if we have not set this explicitly,so this is comparitively very less.the issue stated here points that there is no enough Perm Gen space avaialable as per your current JVM settings,so increase it to avoid this issue.Again you need to select appropriate values based on your  development environment,how much hardware support etc.

You need to modify this in any webLogic startup Script,i had modified this in setDomain.env file.

Increase the heap size to

MEM_ARGS=-Xms_ _ _m -Xmx_ _ _ _ , here i have given values as 512 and 1024 respectievly.

Set the Perm size

MaxPermSize=_ _ _m,the value given here is 512.

Ideally the Max PermGen value allocated to JVM will be 50% of the Max Heap Size(Xmx).

Also typically in a development environment ,if you are using one Admin Server to manage multiple Managed Servers and all your applications are deployed in Managed Servers,then JVM of your Admin Server require less Heap and PermGen space to load only the Out Of The Box Classes,In this case its ideal to decrease the value of Heap and PermGen for the Admin Server JVM from their original default values.I have tried -XX:PermSize=48m  -XX:MaxPermSize=96m,for a 32 bit JVM, which is working fine.

Make sure to take a backup of the original file,
restart the server,ideally this error will disappear.


Next tip

Comments

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration...
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>  ...
Read more

Add a shopping cart button to the product page

-
Make sure you have ATG running with your Application  module. We are adding a jsp page fragment called addcart.jsp . This fragment will use two parameters passed from other jsp, skuInfo.jsp - skuId and productId . Add the form and inputs required to add an item to the order,  as shown in the sample code below: <dsp:input type="hidden" bean="CartModifierFormHandler.catalogRefIds" paramvalue="skuId"/> <dsp:input type="hidden" bean="CartModifierFormHandler.productId" paramvalue="productId"/> <dsp:input type="text" size="5" bean="CartModifierFormHandler.quantity" value="1"/> <dsp:input type="hidden" bean="CartModifierFormHandler.addItemToOrderSuccessURL" value="cart.jsp"/> <dsp:input type="submit" bean="CartModifierFormHandler.addItemToOrder" value="Add to Cart"/> Don't forget to import the /at...
Read more