Java.lang.OutOfMemoryError: heap allocation failed

Hi,
I am facing a strange which i cannot debug..
Could anyone let me know what could be the exact reason for this kind of error...
Exception in thread "172.24.36.74:class=SnmpAdaptorServer_172.24.36.74,protocol=snmp,port=161" java.lang.OutOfMemoryError: heap allocation failed
     at java.net.PlainDatagramSocketImpl.receive0(Native Method)
     at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
     at java.net.DatagramSocket.receive(DatagramSocket.java:712)
     at com.sun.management.comm.SnmpAdaptorServer.doReceive(SnmpAdaptorServer.java:1367)
     at com.sun.management.comm.CommunicatorServer.run(CommunicatorServer.java:617)
     at java.lang.Thread.run(Thread.java:595)
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
Ur help on this is very much appreciated...
Srinivasan.

You are trying to receive a Datagram with an enormous byte array. The maximum size of a UDP datagram is 65535-28=65507 bytes, and the maximum practical size is 534 bytes.
Best practice with UDP is to use a byte array one larger than the largest expected datagram, so you can detect truncations: if the size of the received datagram = the size of the byte array, you received an unexpectedly large message and it has probably been truncated.

Similar Messages

Java.lang.OutOfMemoryError:class Your Java heap size might be set too high.

I am getting the below error while deploying some soa applications in WLS 10.3 on solaris platform.As a workaround,
the server instance has to be restarted everytime i make the deployments when i face this OOM situations.
usually i face this issue after first deployment onwards.
So, everytime i make the next deployment the server instance has to be restarted before that.
The server is configured with 1Gb JVM and runs on JRockit jrrt-4.0.0-1.6.0.
MEM_ARGS="-Xms1g -Xmx1g -Xgcprio:throughput -Xverbose:gc -XX:+HeapDumpOnOutO
fMemoryError -XXcompressedRefs:enable=true"
Can anybody please provide any pointers to track/solve this issue?
Log extract:
####<Oct 10, 2010 4:27:31 PM PST> <Error> <Deployer> <BOX1> <SERVER2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1256893524756> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1256893524756' for task '3'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:118)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.OutOfMemoryError: class allocation, 21977184 loaded, 20M footprint in check_alloc (classalloc.c:213) 1412 bytes requested.
Java heap 1G reserved, 1G committed
Paged memory=18014398507524232K/16781304K.
Your Java heap size might be set too high.
Try to reduce the Java heap
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:335)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:288)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getConstructor0(Class.java:2699)
at java.lang.Class.newInstance0(Class.java:326)
at java.lang.Class.newInstance(Class.java:308)
at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:1058)
at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:1129)
at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:542)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:435)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Its running on Solaris 10 platform.The server is configured with 1Gb JVM and JRockit jrrt-4.0.0-1.6.0.
MEM_ARGS="-Xms1g -Xmx1g -Xgcprio:throughput -Xverbose:gc -XX:+HeapDumpOnOutO
fMemoryError -XXcompressedRefs:enable=true"
Let me know if you need any more information to track this issue.

Java.lang.OutOfMemoryError: HeapSpace

May i know what's the particulare reason about this type of error
java.lang.OutOfMemoryError: heap space
we got this error in my project.
in which case this type of error may occur and what's it's best solution....?
How Can i resolve this error ?
Can i anyone tell me briefly?
please
Best Regards
Ashutosh
S/w Trainee

java.lang.OutOfMemoryError: heap space means VM heap space is not enough for your program. The default VM opts is very small, maybe not suit to your program.
So you can extend your program's VM, using opts. If your program is J2SE, some like use java xxx.class, you can insert opts into command. If your program is J2EE, your can extend your container VM opts.
The opts are the same, insert or change the opts such as "-Xms256m -Xmx1024m" to your program.(The number is suit to your computer).
Note: The Xms is initial Java heap size. The Xmx is maximum Java heap size.

"java.lang.OutOfMemoryError: Java heap space" while trying to read Excel.

Hi Experts,
Here is my query. I'm trying to upload excel data into database table. This excel contains more than 20000 records. I'm storing this data in a vector after reading it & passing this vector as a parameter to another method(not mentioned in the below code) which writes into the database. The code works for records <4000, but fails to read beyond that & throws exception as below.
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Java heap space
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:433)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:355)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
javax.servlet.ServletException: Java heap space
     org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:841)
     org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:774)
     org.apache.jsp.readexcelsap_jsp._jspService(readexcelsap_jsp.java:365)
     org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:331)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
root cause
java.lang.OutOfMemoryError: Java heap space
Below is the code for reference. Kindly Help me in getting this heap space error rectified or suggest me alternate ways.
I tried increasing Heap space as googled but in vain.
<%!
private Vector readExcelSheet(String uploadedFilePath, int sheetNo) throws IOException
     Vector allRowInfo = null;
        try
            HSSFSheet sheet= getWorkSheet(uploadedFilePath,sheetNo);
            //System.out.println(uploadedFilePath);
            //System.out.println(sheetNo);
            //System.out.println("--Sheet--"+sheet);
            //System.out.println("--Sheet--"+sheet.getLastRowNum());
            if(sheet!=null)
            allRowInfo = new Vector();
            for(int i=0;i<=sheet.getLastRowNum();i++)
                HSSFRow row= sheet.getRow(i);
                Vector eachRowInfo = new Vector();
                for(short j=0;j<row.getLastCellNum();j++)
                    eachRowInfo.add(getCellContents(row.getCell(j)));
                    //System.out.println("--"+row.getCell(j));
                allRowInfo.add(eachRowInfo);
            else
                 allRowInfo = null;
            //return allRowInfo;
        catch (FileNotFoundException ex)
             System.out.println("-- Error in reading--getWorkSheet -- 1--"+ex);
             allRowInfo = null;
        catch (IOException ex)
             System.out.println("-- Error in reading--getWorkSheet-- 2 --"+ex);
             allRowInfo = null;
        catch (IndexOutOfBoundsException ex)
             System.out.println("-- Error in reading--getWorkSheet-- 2 --"+ex);
             allRowInfo = null;
        catch (NullPointerException ex)
             System.out.println("-- Error in reading--getWorkSheet --"+ex);
             allRowInfo = null;
        catch(Exception e)
            System.out.println(e.getMessage());
            e.printStackTrace();
             allRowInfo = null;
        return allRowInfo;
%>
<%!
private HSSFSheet getWorkSheet(String uploadedFilePath, int sheetNo) throws IOException
        HSSFSheet sheet = null;
        try
            FileInputStream inputStream=new FileInputStream(uploadedFilePath);
            POIFSFileSystem poisFile=new POIFSFileSystem(inputStream);
            HSSFWorkbook workBook= new HSSFWorkbook(poisFile);
            sheet = workBook.getSheetAt(sheetNo);
        catch (FileNotFoundException ex)
             System.out.println("-- Error in reading--getWorkSheet --"+ex);
             sheet = null;
        catch (IOException ex)
             System.out.println("-- Error in reading--getWorkSheet --"+ex);
             sheet = null;
        catch (IndexOutOfBoundsException ex)
             System.out.println("-- Error in reading--getWorkSheet --"+ex);
             sheet = null;
        catch (NullPointerException ex)
             System.out.println("-- Error in reading--getWorkSheet --"+ex);
             sheet = null;
        catch(Exception e)
            System.out.println(e.getMessage());
            e.printStackTrace();
            sheet = null;
         return sheet;
%>
<%!
public String getCellContents(HSSFCell cell)
        String cellValue="";
        String cellValue1="";
        if(cell!=null)
             int cellType= cell.getCellType();
            if(cellType==HSSFCell.CELL_TYPE_NUMERIC)
                cellValue=(float)cell.getNumericCellValue()+"";
            if(cellType==HSSFCell.CELL_TYPE_STRING)
                 cellValue1=cell.getStringCellValue();
                 StringBuffer sb = new StringBuffer();
                 for(int i = 0; i < cellValue1.length(); i++)
                        sb.append(cellValue1.charAt(i));
                     if(cellValue1.charAt(i)=='\'')
                          sb.append('\'');
                 cellValue = sb.toString();
       return cellValue;
%>
<html>
<body>
<%
     String file_Name="Myexcel.xls";
     String path = "D://Test Upload//"+file_Name;
     Vector list = readExcelSheet(path,0);
</html>
</body>Regards
Venky
Edited by: Venky_86 on Jun 17, 2009 6:05 AM

HOW did you increase the heap space? As that is the only solution you have in this case really.
It is a known fact that POI can use up a lot of memory for big spreadsheets. If at all possible, I would try to switch to plain text comma separated files / tab delimited files. If you cannot do that, I would try to put a size restriction on the sheets that your application will process to get rid of the heap space risk. A sheet can contain 20000 records, or four sheets can contain 5000 records; in both cases you process the exact same data, but at only 25% of the total memory usage.

XML Publisher report failing with java.lang.outofmemoryerror.

Hi,
We have developed a custom Oracle report that produces an XML output file that is about 13M in size (about 18K rows from the database). When running report as concurrent request, post processing fails with java.lang.outofmemoryerror. The failure occurs when specifying output format as Excel, RTF or HTML. However, the process completes successfully when specifying output format as PDF. We have also noticed that Excel, RTF and HTML will complete successfully if the XML data file is smaller (around 3M).
Is anyone aware of a restriction on the size of the XML data file when specifying output formats Excel, RTF or HTML? We have tried setting temp directory but that has not helped.
Thanks.

Hi
I found this at metalink [Note:390968.1].. hope it helps =)
Symptoms: When attempting to run an XML Publisher concurrent program the following error occurs:
ERROR: Warning!!! Got out of memory exception, retrying with scalable option..
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
Oracle.apps.xdo.oa.cp.JCP4XDODataEngine
Program exited with status 1
Solution: To implement the solution, please execute the following steps:
1. Login select the responsibility: System Administrator.
2. Navigate to Concurrent > Program > Define.
3. Query for concurrent program that is receiving the error.
4. In the 'Options' field please enter -Xmx512M.
5. Save the change and retest the issue.
6. If the report still fails with the option set to -Xmx512M change the value to -Xmx1024M, save and try again
7. Migrate the solution as appropriate to other environments.

EJB Deployment error in 9.2 (java.lang.OutOfMemoryError: Java heap space at

Hello all,
I am trying to deploy EAR(has more than 25 ejb's) in weblogic 9.2 but currently one EJB ejb-pwc.jar is failing to compile(gives out of memory error). But if i try building ear only with this EJB and its dependencies class it work. Here is the errror. Please help me to figure out this issue. Thanks in advance,
Exception preparing module: EJBModule(ejb-pwc.jar) Unable to deploy EJB: ejb-pwc.jar from ejb-pwc.jar: There are 1 nested errors: java.io.IOException: Compiler failed executable.exec: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435) at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295) at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303) at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:308) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:496) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:463) at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430) at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752) at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Compiler failed executable.exec: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space

I'd suggest pre-compiling the application before deployment.
java weblogic.appc my.ear
(You may need to increase the heap size here as well.)
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Deployment error in 9.2 (java.lang.OutOfMemoryError: Java heap space at we)

Hello all,
I am trying to deploy EAR(has more than 25 ejb's) in weblogic 9.2 but currently one EJB ejb-pwc.jar is failing to compile(gives out of memory error). But if i try building ear only with this EJB and its dependencies class it work. Here is the errror. Please help me to figure out this issue. Thanks in advance,
Exception preparing module: EJBModule(ejb-pwc.jar) Unable to deploy EJB: ejb-pwc.jar from ejb-pwc.jar: There are 1 nested errors: java.io.IOException: Compiler failed executable.exec: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435) at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295) at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303) at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:308) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:496) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:463) at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430) at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752) at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:621) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:208) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Compiler failed executable.exec: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space

I'd suggest pre-compiling the application before deployment.
java weblogic.appc my.ear
(You may need to increase the heap size here as well.)
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

How to solve : java.lang.OutOfMemoryError: Java heap space

Dear all,
Am using Jdeveloper 11.1.1.3 with weblogic10...
I keep getting out of memory error while working on the application , here is the exact error message that i copied from the server log :
####<28/11/2010 GMT 09:17:58 ص> <Critical> <Health> <javaserver> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-0000000000000012> <1290935878582> <BEA-310003> <Free memory in the server is 4,541,416 bytes. There is danger of OutOfMemoryError>
####<28/11/2010 GMT 09:24:51 ص> <Error> <Kernel> <javaserver> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-0000000000000029> <1290936291218> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
>
####<28/11/2010 GMT 09:25:04 ص> <Notice> <Diagnostics> <javaserver> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002c> <1290936304406> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'AdminServer' has triggered at 28/11/2010 GMT 09:24:56 ص. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: DATE = 28/11/2010 GMT 09:24:51 ص SERVER = AdminServer MESSAGE = ExecuteRequest failed
java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
SUBSYSTEM = Kernel USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-000802 MACHINE = javaserver TXID = CONTEXTID = 3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-0000000000000029 TIMESTAMP = 1290936291218
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 30000
>
####<28/11/2010 GMT 09:25:36 ص> <Warning> <oracle.dfw.framework> <javaserver> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002c> <1290936336549> <DFW-40121> <failure creating incident from WLDF notification
java.lang.OutOfMemoryError: Java heap space
>
####<28/11/2010 GMT 09:26:32 ص> <Notice> <WebLogicServer> <javaserver> <AdminServer> <Thread-1> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002f> <1290936392224> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<28/11/2010 GMT 09:26:35 ص> <Alert> <WebLogicServer> <javaserver> <AdminServer> <Thread-1> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002f> <1290936395303> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<28/11/2010 GMT 09:26:35 ص> <Notice> <WebLogicServer> <javaserver> <AdminServer> <Thread-1> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002f> <1290936395303> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
####<28/11/2010 GMT 09:26:53 ص> <Notice> <WebLogicServer> <javaserver> <AdminServer> <Thread-1> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002f> <1290936413632> <BEA-000365> <Server state changed to ADMIN>
####<28/11/2010 GMT 09:26:56 ص> <Notice> <WebLogicServer> <javaserver> <AdminServer> <Thread-1> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002f> <1290936416757> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<28/11/2010 GMT 09:26:59 ص> <Notice> <Server> <javaserver> <AdminServer> <DynamicListenThread[Default[1]]> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-0000000000000035> <1290936419289> <BEA-002607> <Channel "Default[1]" listening on 127.0.0.1:7001 was shutdown.>
####<28/11/2010 GMT 09:27:07 ص> <Notice> <WebLogicServer> <javaserver> <AdminServer> <Thread-41> <<WLS Kernel>> <> <3e9ac2aaa3059905:3bfb8868:12c91bef422:-8000-000000000000002f> <1290936427508> <BEA-000378> <Server failed to shutdown within the configured timeout of 30 seconds. The server process will exit now.>
i searched the net and it seems that i should increase the java heap size , how can i do that... I have a server with 4G Ram ..
Regards,
Lama
Edited by: Delta on Nov 28, 2010 1:36 AM

My frien google tells me that you use
>
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
This can have two reasons:
* Your Java application has a memory leak. There are tools like YourKit Java Profiler that help you to identify such leaks.
* Your Java application really needs a lot of memory (more than 128 MB by default!). In this case the Java heap size can be increased using the following runtime parameters:
java -Xms<initial heap size> -Xmx<maximum heap size>
>
Timo

Java heap space java.lang.OutOfMemoryError coming in weblogic server

Hi All,
I am getting following out of memory exception on BCC server start up.
<Nov 13, 2013 3:17:09 AM IST> <Critical> <Health> <BEA-310003> <Free memory in the server is 1,134,688 bytes. There is danger of OutOfMemoryError>
Exception in thread "Timer-2" java.lang.OutOfMemoryError: Java heap space
        at java.util.AbstractCollection.toArray(AbstractCollection.java:119)
        at java.util.ArrayList.<init>(ArrayList.java:131)
        at javax.jmdns.impl.DNSCache.getCacheNodes(DNSCache.java:223)<Nov 13, 2013 3:17:28 AM IST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
        at javax.jmdns.impl.tasks.RecordReaper.run(RecordReaper.java:48)
        at java.util.TimerThread.mainLoop(Timer.java:512) java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
        at java.util.TimerThread.run(Timer.java:462)
        at java.lang.reflect.Array.newArray(Native Method)
Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: Java heap space
        at java.lang.reflect.Array.newInstance(Array.java:52)   at java.lang.reflect.Array.newArray(Native Method)
        at java.lang.reflect.Array.newInstance(Array.java:52)
        at java.util.AbstractCollection.toArray(AbstractCollection.java:159)    at java.util.AbstractCollection.toArray(AbstractCollection.java:159)
        at java.util.Collections$SynchronizedCollection.toArray(Collections.java:1569)
        at atg.service.jdbc.FakeXAResource.recover(FakeXAResource.java:430)
        at weblogic.transaction.internal.XAServerResourceInfo.recover(XAServerResourceInfo.java:1019)   at java.util.Collections$SynchronizedCollection.toArray(Collections.java:1569)
        at weblogic.transaction.internal.ServerSCInfo.recover(ServerSCInfo.java:645)
        at weblogic.transaction.internal.XAResourceDescriptor.getXidsToBeRolledBack(XAResourceDescriptor.java:1137)
        at atg.service.jdbc.FakeXAResource.recover(FakeXAResource.java:430)
        at weblogic.transaction.internal.XAResourceDescriptor.recover(XAResourceDescriptor.java:1073)
        at weblogic.transaction.internal.XAResourceDescriptor.access$100(XAResourceDescriptor.java:60)
        at weblogic.transaction.internal.XAResourceDescriptor$2.run(XAResourceDescriptor.java:823)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
        Truncated. see log file for complete stacktrace
I think this can't be issue with following variables:As I hv set them from 64m to 256, still issue coming.
WLS_MEM_ARGS_32BIT=-Xms200m -Xmx256m
MEM_PERM_SIZE_32BIT=-XX:PermSize=200m
MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=256m
Any suggestion.
Thanks,
Nitin.

making it 512 temporarily working fine, but my concern was something must have been eating all the memory.
I did run bcc with 128 MB and deployed lots of initial data too, didn't face the issue in recent past with same versions and same build size.
ATG:10.2
Weblogic: 10.3.5
JDK:1.6.0_25
One more info:
my build size is around 200 MB
I m not running productionAgent,But I didn't make that essential while setting agent.
Can that be issue that some Manager trying to hit the server continuously and eating the memory.
Can not running the agent server, eat substantial memory?
**** Warning
Wed Nov 13 04:25:21 IST 2013
1384296921718   /atg/epub/DeploymentServer
Failed to connect to agent 'ProdcutionAgent'. 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.
@others:
BCC Server memory parameters:
WLS_MEM_ARGS_32BIT=-Xms512m -Xmx512m
MEM_PERM_SIZE_32BIT=-XX:PermSize=128m
MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=256m
Production Server memory parameters:
WLS_MEM_ARGS_32BIT=-Xms200m -Xmx256m
MEM_PERM_SIZE_32BIT=-XX:PermSize=64m
MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=128m

Servlet failed with Exception java.lang.OutOfMemoryError: PermGen space

Hello,
I recently installed BI Apps 11.1.1.7.1 on Oracle Linux 64.
while i am trying to run the full load i.e. SDE, SILOS and PLP and sometimes while trying to access BIA Configuration Manager..I get below error. while i tried to increase the heap size to 2gb in SetOBIDomain.sh for both bi_server1 and odi_sever1.sh, it is not really affected i.e. i dont see the updated arguments while trying to re start these managed servers. i tried to restart the box and it still did not work...Any idea on where exactly to change/update the parameters to increase the heap size and any other known issues cauing out of memory issues.
<Sep 30, 2013 11:55:44 AM EDT> <Error> <HTTP> <BEA-101020> <[ServletContext@263264514[app:oracle.biacm module:biacm path:/biacm spec-version:2.5 version:11.1.1.7.1]] Servlet failed with Exception
java.lang.OutOfMemoryError: PermGen space
Thank You in advance
Rakesh

Hi Fabian,
It seems that you have got out of memory due to PermGen space, hence increase the MaxPermGen space
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
Also you can go through the below posts to get more details about JVM architecture and more details about Out of memory
Topic: Parts Of JVM And JVM Architecture Diagram?
http://middlewaremagic.com/weblogic/?p=4456
Topic: OutOfMemory Causes and First Aid Steps?
http://middlewaremagic.com/weblogic/?p=4464
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

Getting java.lang.outofmemoryerror: Java heap space error

I am using coldfusion 8. I frequently get the error 'java.lang.outofmemoryerror: Java heap space'. Can anyone help me?
Error Details :
500
Root cause:
java.lang.outofmemoryerror: Java heap space
javax.servlet.servletException: Root Cause:
java.lang.outofmemoryerror: Java heap space
Thanks in advance,
Regards,
Satheesh.

Well... what does the error message tell you is wrong? You're running out of memory. I presume you understand how computer memory works, if not specifically how Java memory allocation works. So... you have x amount of memory, and you're trying to use >x amount of memory. You can't do that. There are two approaches to dealing with a problem like this:
a) have more memory;
b) use less memory.
What are your JVM memory settings? They're in jvm.config dir, which'll be - by default - in your Jrun4/bin dir for a multi-server install, or somewhere like ColdFusion/runtime/bin or something like that on a stand-alone install.
Next... what are you loading into memory? This is trickier to answer. But every variable you create takes up memory. People often load up the application or session scopes with stuff that's "convenient" to store in shared-scope memory, but really chew through it. Putting CFC instances in the session scope is a really good way to waste memory, as they seem to have quite a large footprint.
It's really impossible to say what's eating the memory based on what info you've given us (basically: none), but you can use things like FusionReactor to examine what's going into memory. Or CF* Enterprise has some of its own memory profiling stuff... I've never used it but it might be of some use.
Have you googled "coldfusion java.lang.outofmemory"?
Adam

OAS Heap memory issue: An error "java.lang.OutOfMemoryError: GC overhead

OAS - 10.1.3.4.0
We are running out of Heap memory and seeing lots of full GC and out of memory events
Verbose GC is on.
Users don't know what they are doing to cause this
We have 30-40 users per server and 1.5 GB heap memory allocated
There are no other applications on the machine. Only the PRD instance with 1.5 GB allocated to the JVM. We do not have any issue with memory on the server and we could increase the heap but we dont want to go over the 1.5 GB since that is what I understood to be the high end of what is recommended. we only have 30-40 users on each machine. There are 8 servers and a typical heavy usage day we may have 1 or two machines that have the out of memory or continuous full GC in the logs. When this occurs the phones light up with the people on that machine experiencing slowness.
below is an example of what we see in a file created in the OPMN log folder on the JAS server then this occurs. I think this is the log created when Verbose GC is turned on. I can send you the full log or anything else you need. Thanks
1194751K->1187561K(1365376K), 4.6044738 secs]
java.lang.OutOfMemoryError: GC overhead limit exceeded
Dumping heap to java_pid10644.hprof ...
[Full GC 1194751K->1188321K(1365376K), 4.7488200 secs]
Heap dump file created [1326230812 bytes in 47.602 secs]
[Full GC 1194751K->1177641K(1365376K), 5.6128944 secs]
[Full GC 1194751K->986239K(1365376K), 4.6376179 secs]
[Full GC 1156991K->991906K(1365376K), 4.5989155 secs]
[Full GC 1162658K->1008331K(1365376K), 4.1139016 secs]
[Full GC 1179083K->970476K(1365376K), 4.9670050 secs]
[GC 1141228K->990237K(1365376K), 0.0561096 secs]
[GC 1160989K->1012405K(1365376K), 0.0920553 secs]
[Full GC 1012405K->1012274K(1365376K), 4.1170216 secs]
[Full GC 1183026K->1032000K(1365376K), 4.4166454 secs]
[Full GC 1194739K->1061736K(1365376K), 4.4009954 secs]
[Full GC 1194739K->1056175K(1365376K), 5.1124431 secs]
[Full GC 1194752K->1079807K(1365376K), 4.5160851 secs]
in addition to the 'overhead limit exceded' we also will see :
[Full GC 1194751K->1194751K(1365376K), 4.6785776 secs]
[Full GC 1194751K->1188062K(1365376K), 5.4413659 secs]
[Full GC 1194751K->1194751K(1365376K), 4.5800033 secs]
[Full GC 1194751K->1194751K(1365376K), 4.4951213 secs]
[Full GC 1194751K->1194751K(1365376K), 4.5227857 secs]
[Full GC 1194751K->1171773K(1365376K), 5.5696274 secs]
11/07/25 11:07:04 java.lang.OutOfMemoryError: Java heap space
[Full GC 1194751K->1183306K(1365376K), 4.5841678 secs]
[Full GC 1194751K->1184329K(1365376K), 4.5469164 secs]
[Full GC 1194751K->1184831K(1365376K), 4.6415273 secs]
[Full GC 1194751K->1174738K(1365376K), 5.3647290 secs]
[Full GC 1194751K->1183878K(1365376K), 4.5660217 secs]
[Full GC 1194751K->1184651K(1365376K), 4.5619460 secs]
[Full GC 1194751K->1185795K(1365376K), 4.4341158 secs]

There's an Oracle support note with a very similar MO :
WebLogic Server: Getting "java.lang.OutOfMemoryError: GC overhead limit exceeded" exception with Sun JDK 1.6 [ID 1242994.1]
If I search for "java.lang.OutOfMemoryError: GC overhead" on Oracle Support it returns at least 12 documents
Might be bug 6065704. Search Oracle support for this bug number.
Best Regards
mseberg

Servlet.service() Error. java.lang.OutOfMemoryError: Java heap space

Hi All,
I would be very grateful if you would draw some light for this error I got from running a online database connected image viewer (applet).
The application is quite simple, applet connect to servlet, servlet send 3 SQL statements to MySQL and retrieve image info (Strings) and 50 Files (- JPEG image) from a online database, and then pass all of data to applet from servlet. The size of total of images is around 3.5 MB, and I've increased JVM memory to 128 MB by using code "-xmx128m".
? Do I need send images from servlet to applet individually rather than push them in one go
? Is there memory leak in my codes
Please see the codes below:
private ExamViewerApplet.CaseInfo[] getCaseInfoArray(int examID, Connection conn) throws SQLException{...}
private ExamViewerApplet.ExamInfo getExamInfo(int examID, Connection conn) throws SQLException{...}
private String processObject(Object object, ObjectOutputStream oos)    {
    Integer examID = (Integer) object;
    Connection conn = null;
    ExamViewerApplet.ExamInfo examInfo = null;
    ExamViewerApplet.CaseInfo caseInfoArray[] = null;
    int[][] imageIndexArray = new int[30][5];
    ImageIcon[] imageArray = null;
    try {
        conn = new DBConnection().getConnection();
        examInfo = this.getExamInfo(examID, conn);
        caseInfoArray = this.getCaseInfoArray(examID, conn);
        PreparedStatement ps = conn.prepareStatement(RETRIEVE_IMAGES);
        ps.setInt(1,examID);
        ResultSet rs = ps.executeQuery();
        rs.last();
        int size = rs.getRow();
        rs.beforeFirst();
        imageArray = new ImageIcon[size];
        int imageIndex = 0;
        while(rs.next()){
            int caseID = rs.getInt("CaseID");
            int imageID = rs.getInt("ImageID");
            InputStream stream = null;
            ByteArrayOutputStream output = null;
            try {
                stream = rs.getBinaryStream("Image");
                output = new ByteArrayOutputStream();
                byte buf[] = new byte[1024];
                int len;
                while((len = stream.read(buf)) > 0){
                    output.write(buf, 0, len);
                ImageIcon icon = new ImageIcon(output.toByteArray());
                imageArray[imageIndex] = icon;
                imageIndexArray[caseID][0] += 1;
                imageIndexArray[caseID][imageID] = imageIndex;
                ++imageIndex;
            } catch (IOException ex) {
                log("Error, when reading byte array from image input stream from database");
            } finally{
                try {
                    stream.close();
                    output.close();
                } catch (IOException ex) {
                    log("Error, when tring to close image input stream from Database");
    } catch (ClassNotFoundException classNotFoundException) {//somecode...
    } catch (SQLException sQLException) {//somecode...
    }finally{
        try {
            conn.close();
        } catch (SQLException ex) {//somecode...
    String result;
    if(examInfo != null && caseInfoArray != null && imageIndexArray != null && imageArray != null ){
        result = "The transaction was successed!";
        try {
            oos.writeObject(examInfo);
            oos.writeObject(caseInfoArray);
            oos.writeObject(imageIndexArray);
            oos.writeObject(imageArray);
        } catch (IOException ex) {
            result = "The transaction was failed!";
    }else{
        result = "The transaction was failed!";
    return result;
protected void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
    ObjectInputStream inputStreamFromApplet = null;
    Object object = null;
    try {
        inputStreamFromApplet = new ObjectInputStream(request.getInputStream());
        object = inputStreamFromApplet.readObject();
        ObjectOutputStream oos = new ObjectOutputStream(response.getOutputStream());
        String returnValue = this.processObject(object, oos);
        oos.writeObject(returnValue);
        oos.flush();
        oos.close();
    } catch (ClassNotFoundException classNotFoundException) {
        classNotFoundException.printStackTrace();
    } finally{
        inputStreamFromApplet.close();
} And the error messages I got here is:
SEVERE: Servlet.service() for servlet ExamViewerServlet threw exception
java.lang.OutOfMemoryError: Java heap space
        at javax.swing.ImageIcon.writeObject(ImageIcon.java:411)
        at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:592)
        at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
        at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
        at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1251)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
        at ExamViewerServlet.processObject(ExamViewerServlet.java:147)
        at ExamViewerServlet.processRequest(ExamViewerServlet.java:176)
        at ExamViewerServlet.doPost(ExamViewerServlet.java:217)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
        at java.lang.Thread.run(Thread.java:595)Please help.
Linqing
Edited by: discovery_java on Feb 1, 2010 2:12 PM

wire the code into a simple unit test, then run a profiler on it to see where the memory is going. You need the help of these kind of tools to track down memory issues, before that it is only guesswork what might be soaking it all up.

Tomcat Error: "java.lang.OutOfMemoryError: Java heap space"

Hi,
We are on BOXI 3.1 SP3. We are using Tomcat as a application server.
After certain time interval tomcat server hangs and users are unable to login to Infoview. When we checked in catalina.out file, we got error "java.lang.OutOfMemoryError: Java heap space". As a workaround, we restart tomcat server. That time we are unable to stop tomcat server using tomcatshutdown.sh script and we need to kill it forcefully. Once we restart the tomcat server, occupied memory free up and users are able to login to Infoview.
Below are my observations on this issue:
1. We have observed that this is not happening only during peak time/heavy load on system, but is happening during weekend as well which shows that it is not related to user load.
2. Issue occurs intermittently.
3. Tomcat is unable to release unused memory. It just adds the memory and reaches it's maximum allocated memory.
I raised SAP case for this and they suggested to add parallet garbage collector parameter. but that did not help.
Below is heap size setting for Java under /Install Dir/setup/env.sh:
JAVA_OPTS="$JAVA_OPTS -Xmx1024m -XX:MaxPermSize=256m -XX:+UseParallelGC"
Below are my environment details:
Product : BOXI R3.1 SP3
Linux: Redhat 5.3
RAM: 10 GB
Web Application Server : Apache - Tomcat
I am thinking that somehow tomcat is unable to free up it's occupied memory which is not used by any object further. It just keeps adding memory and reaches its maximum threshold limit which is 1024 MB.
We have installed SP3 on server last Sunday. Issue was there before SP3 installation as well and it was occuring very rarely. But after SP3 installation, it is occuring on daily basis. Is there any known bug in SP3.
Any help would be greatlt appericiated.
Thanks,
Swapnil Rodge.

Hi Sebastian,
Did you use the -Xmx2048m setting for Tomcat? If yes, how did it work for you? When I do the same tomcat refuses to start.
Thanks,
Vinayak

Report error trace ![CDATA[java.lang.OutOfMemoryError: Java heap space

Hi,
I am getting the below error while trying to run any report in workspace
<?xml version="1.0" encoding="UTF-8"?>
<BpmResponse action="" type="error">
<code>0</code>
<desc>Java heap space</desc>
<trace><![CDATA[java.lang.OutOfMemoryError: Java heap space
]]></trace>
</BpmResponse>
Looking for a qucik response!!!
Thanks
Ramya

You are running out of memory. You can change the allocated java heap space for reporting if you haven't tried that already.
Here is a thread regarding how to change the java heap space. Oracle recommends setting your -xmx to 1024.
JVM Heap Size setting
Hope this helps,
DQ

Java.lang.OutOfMemoryError: heap allocation failed

Similar Messages

Maybe you are looking for