Showing posts with label HEAP-SIZE. Show all posts
Showing posts with label HEAP-SIZE. Show all posts

Tuesday, July 8, 2014

THE DEFAULT SETTINGS FOR JVM HEAP SIZE MAY NOT BE ADEQUATE FOR LARGE ENVIRONMENTS

By default, we set the Maximum Heap size to 1024.

This may cause a problem with memory available to WAS:

Exceptions visible in the logs:

2012/05/30 11:30:47:545 CAT] 00000016 TimerImpl     E ASYN0012E:  Alarm/Timer threw exception commonj.work.WorkCompletedException: java.lang.RuntimeException: java.lang.OutOfMemoryError
Caused by: java.lang.OutOfMemoryError  at java.lang.String.(String.java:365) at com.ibm.license.mgmt.dao.ProductReplacementDAO$ReplacingBranchVO.depure(Unknown Source)  at com.ibm.license.mgmt.dao.ProductReplacementDAO$ReplacingBranchVO.(Unknown Source)  at com.ibm.license.mgmt.dao.ProductReplacementDAO.getBranch(Unknown Source)

This may happen during aggregation, catalog import,recalculation.

Local fix
a) increase the WebSphere JVM memory, by navigating  from Tivoli
Integrated Portal to  > Settings > WebSphere Administrative Console > Launch console

 > In the WebSphere web console, select Servers -> Server Types

WebSphere application servers -> Server Infrastructure -> Java and Process Management -> Process definition

 > In Additional Properties section, select Java Virtual Machine

 > In General Properties section, increase the values for "Initial heap size" and for "Maximum heap size".

b) restart the server

In some cases reverting aggregation process may be necessary.

source : http://www-01.ibm.com/support/docview.wss?uid=swg1IV22047


Generate reports from Opportunities using a Visualforce Page in Salesforce

  Step 1: Create a Visualforce Page Go to the Setup menu in Salesforce. Search for "Visualforce Pages" in the Quick Find box and c...