Oracle WebLogic 10.0 MP2 Installation error: Java Heap Space

Dear All,
Installing weblogic 10.0 MP2 gave the following error "Exception in thread 'Thread 26' java.lang.OutOfMemoryError Java Heap Space"
The installation progress bar stops at 92% . I tried to install many times and am not successfull.
Please help/provide suggestions on how to solve the intallation error.
Processor: Intel Quad core 64bit
OS: windows server 2008 R2 64 bit
Java: JDK 1.5 update 21 64 bit
Weblogic: Server 10.0 MP2 64 bit for windows
Thanks,
Regards,

Hi,
Looks like you are using Generic Jar installer...so in that case please run the installer by using the -Xmx1024m option:
Example:
JAVA_HOME/bin/java -jar -Xmx1024m wls1001_generic.jar
As suggested in the following link: http://middlewaremagic.com/weblogic/?p=2731
Thanks
Jay SenSharma

Similar Messages

When I try to load an image from the scanner, or from a file, into a bank deposit script, I get a message - "Error Java heap space". Need help to diagnose and fix this problem.

I am running a script from my banking facility which asks me to load an image of the front and back of the check. I never had a problem before, but this time when I try to load the images either directly from the scanner, or from previously saved jpg files I get an error window message that says - Error Java heap space,
Ed Marcato

I am running a script from my banking facility which asks me to load an image of the front and back of the check. I never had a problem before, but this time when I try to load the images either directly from the scanner, or from previously saved jpg files I get an error window message that says - Error Java heap space,
Ed Marcato

Flash Builder 4.6 Java Heap Space Error

Hi,
I get this error "Java Heap Space" when trying to clean build (or build in any way) my project.
I have a lot of embeded assets (png, mp3 and some binary files embeded to be read as a ByteArray) which total about 37 MB. Including one more 1.6MB binary asset causes this error to occur.
I have tried to change my memory settings about (-Xmx and -Xms) as previous posts have suggested but this doesn't seem to make any difference.
Is there any patch or solution to this very frustrating limitation of Flash Builder?
Thanks for any help!
Tom

I constantly had issues with this. I managed to run into the max for increasing the heap space. I was able to get beyond the limit by flagging the FlashBuilder.exe file to allow it to allocate to higher memory address ranges. I'm on a 64 bit machine, so the only limitation was the 32 bit FlashBuilder process. Anyways i was able to get from 1024m up to 1720m. Also note that FlashBuilder 4.7 Beta is out and it is a native 64 bit application, so you will get higher addressing there. I just found it to be too buggy for my every day development tasks. Also missing the Design view really hurts development. I hope they put that back in.
Here's more detail on how I got beyond the java heap ceiling.
http://chrsmrtn.azurewebsites.net/flash-builder-java-heap-errors-limitations-of-xms-and-xm x/

Java heap space error occured during message mapping of FILE to IDOC

hello Friends,
I am trying to do the message mapping for File to Idoc scenario.
Idoc which I am using is HRMD_A.HRMD_A06 and infotype which I want to update is 14. I am trying to map the message type which I hav created for infotype 14 with the IDOC
Its very simple scenerio but every time I try to save the mapping before activating it I get an error:
Java heap space
Internal problem occurred (INTERNAL_PROBLEM)
Java heap space.
I am not able to figure out what possibly is the problem wheather its from my end or the BASIS end.
Kindly help.
Regards,
Lokesh

As the server probably survives (you restart your Integration Builder and can probably connect immediately), the problem will be on your side (client). Did you add one or more large xml-test-instances to the mapping ? If yes, delete them, because they lower the performance and can make problems. If not, then this is a strange problem. Even if the Idoc structure is complex, the mapping object itself cannot be that large.Is this problem only with this one mapping ?
CSY
Edited by: Christian Sy on Mar 9, 2010 6:26 AM

Large Report Errors out with Java Heap Space in EBS 12.0.6

When running custom or Standard BI report that have a huge data , we get a following error in EBS
[UNEXPECTED] [156627:RT4605044] java.lang.OutOfMemoryError: Java heap space
at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:45)
at java.lang.StringBuffer.<init>(StringBuffer.java:91)
at oracle.apps.xdo.template.fo.FOHandler.init(FOHandler.java:161)
at oracle.apps.xdo.template.fo.FOProcessingEngine.process(FOProcessingEngine.java:335)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:1045)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5926)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3458)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3547)
at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:259)
at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
We have tried the follwing workaroud mentioned in the docoment 737311.1
A)
1)update FND_CP_SERVICES set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx5120m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
2)As XML Publisher Administrator navigate to Administration->Configuration.
Under Temporary Directory pick a temporary file location on your concurrent processing node. This should be at least 5GB or 20x larger than largest XML data file you generate
Under FO Processing, set:
Use XML Publisher's XSLT processor set to True
Enable scalable feature of XSLT processor set to False (see #4 below),
Enable XSLT runtime optimization set to True
3)We also have tried to to apply the workaround mentioned in the document 747750.1
In to Concurrent -> Program -> Define, in the 'Executable' group, there is a field named 'Options'.
Enter the value '-ms1024m -mx1024m' as the value for this field.
None of these seem to have worked.
Also refered to the the previous forum entries on these. But did not find anything specific to EBS. Most of them were related to Standalone installations.
CAn anyone help me.
Dhaval K

hi gurus
The problem has sovled.I supplyed the wrong file for the rawfile.conf,everything was fine after I provided the corrent one.
Thanks for your time.

Java heap space error: OutOfMemoryError

Hi,
We are getting below error when we XML Publisher report.
Oracle XML Publisher version is: 5.6.3
We have followed below things to get rid off this error but there is no success.
Log in as XML Publisher Administrator.
Select Templates, then query up the Template for your report.
Select Edit Configuration:
Under FO Processing
Use XML Publisher's XSLT processor set to True
Enable scalable feature of XSLT processor set to True
Enable XSLT runtime optimization set to True.
Set the JVM Heap size using following SQL query
SQL> update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m'
where SERVICE_ID =
(select MANAGER_TYPE
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
Set the following properties from XML Publisher Administration
Responsibility=>Administration UI
General => Temporary directory => \tmp
directory tmp has full read and write access
After above steps performed, bounced CM but still getting below error.
Please provide your valuable suggestions or work arounds on this issue.
Complete error is as below:
[122613_114019363][][EXCEPTION] [DEBUG] [sun.cpu.endian]:[little]
[122613_114019363][][EXCEPTION] [DEBUG] [sun.cpu.isalist]:[]
--XDOException
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java:677)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:425)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:244)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:182)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1044)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:997)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:212)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1665)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:975)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5936)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
at oracle.apps.xdo.oa.cp.JCP4XMLPublisher.runProgram(JCP4XMLPublisher.java:684)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
at java.lang.StringBuffer.append(StringBuffer.java:224)
at oracle.xdo.parser.v2.XMLNSNode.getText(XMLNSNode.java:741)
at oracle.xdo.parser.v2.XMLNSNode.getText(XMLNSNode.java:739)
at oracle.xdo.parser.v2.XMLNSNode.getText(XMLNSNode.java:739)
at oracle.xdo.parser.v2.XSLExprItem.getStringValue(XSLExprItem.java:318)
at oracle.xdo.parser.v2.XSLExprItem.compareVal(XSLExprItem.java:445)
at oracle.xdo.parser.v2.XSLExprValue.compare(XSLExprValue.java:881)
at oracle.xdo.parser.v2.ComparisonExpr.evaluate(XSLExpr.java:1469)
at oracle.xdo.parser.v2.XSLCondition.testCondition(XSLCondition.java:185)
at oracle.xdo.parser.v2.XSLCondition.processAction(XSLCondition.java:165)
at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java:180)
at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java:417)
at oracle.xdo.parser.v2.XSLTemplate.processAction(XSLTemplate.java:191)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:512)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:489)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:271)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:155)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

1. Have you tried also with 'mx1024m' ?
2. Have you run CMCLEAN ?
3. What are these profiles set to:
Concurrent:OPP Process Timeout
Concurrent:OPP Response Timeout
Thank you
Eugen

Java Heap Space error while reading from Excel

Hello,
I have a data flow which reads from excel and updates records in an oracle table.
When the data flow tries to read the excel I get a java Heap space Error.
Error preparing to read <SUPP_STG3_FILE1>: <Java heap space>.
Data flow <DF_SUPP_STG3_UPD> is terminated due to error <58105>.
I have configured Excel Adapter since the server is on UNIX. BOExcelAdapter shows status as red once the execution fails. Before that BOExcel adapter status is green.
BOExcelAdapter Trace:
1/13/12 10:57:38 PM Thread[Thread-6,5,main]      Received an error message from the message broker. [Communication failure. Read timed out]. Will exit adapter immediately.
1/13/12 10:57:47 PM Thread[main,5,main]      Create broker client for life-cycle management. Host:port = hikalxboes01:4001
1/13/12 10:57:47 PM Thread[main,5,main]      Create broker client for data exchange with ASP. Host:port = hikalxboes01:4001. Client ID = com.acta.adapter.msexceladapter.MSExcelAdapter.data_18
1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Create broker client for real-time services with ASP. Host:port = 'hikalxboes01:4000''.
1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Start instance [BOExcelAdapter] of adapter [com.acta.adapter.msexceladapter.MSExcelAdapter].
1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Register the client ID [com.acta.adapter.msexceladapter.MSExcelAdapter.data_18] and adapter destination [hikalxboes01:4001] with the adapter manager.
1/13/12 10:57:47 PM Thread[Thread-11,5,main]      Registration complete.
1/13/12 10:58:10 PM Thread[Thread-10,5,main]      java.lang.OutOfMemoryError: Java heap space
     at org.apache.poi.hssf.usermodel.HSSFRow.addCell(HSSFRow.java:273)
     at org.apache.poi.hssf.usermodel.HSSFRow.createCellFromRecord(HSSFRow.java:196)
     at org.apache.poi.hssf.usermodel.HSSFSheet.setPropertiesFromSheet(HSSFSheet.java:183)
     at org.apache.poi.hssf.usermodel.HSSFSheet.<init>(HSSFSheet.java:128)
     at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:283)
     at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:196)
     at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:178)
     at com.acta.adapter.msexceladapter.MSExcelAdapterReadTable.begin(MSExcelAdapterReadTable.java:537)
     at com.acta.adapter.sdk.StreamOperationWrapper.beginStream(StreamOperationWrapper.java:88)
     at com.acta.adapter.sdk.AdapterRunnerImpl.processBeginOperation(AdapterRunnerImpl.java:1762)
     at com.acta.adapter.sdk.AdapterServiceDataListener.handleBrokerMessage(AdapterServiceDataListener.java:90)
     at com.acta.brokerclient.BrokerClient.handleMessage(BrokerClient.java:439)
     at com.acta.brokerclient.BrokerClient.access$100(BrokerClient.java:53)
     at com.acta.brokerclient.BrokerClient$MessageHandler.run(BrokerClient.java:1621)
     at com.acta.brokerclient.ThreadPool$PoolThread.run(ThreadPool.java:100)
BOExcelAdapter Error Log:
1/13/12 10:58:10 PM      java.lang.OutOfMemoryError: Java heap space
     at org.apache.poi.hssf.usermodel.HSSFRow.addCell(HSSFRow.java:273)
     at org.apache.poi.hssf.usermodel.HSSFRow.createCellFromRecord(HSSFRow.java:196)
     at org.apache.poi.hssf.usermodel.HSSFSheet.setPropertiesFromSheet(HSSFSheet.java:183)
     at org.apache.poi.hssf.usermodel.HSSFSheet.<init>(HSSFSheet.java:128)
     at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:283)
     at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:196)
     at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:178)
     at com.acta.adapter.msexceladapter.MSExcelAdapterReadTable.begin(MSExcelAdapterReadTable.java:537)
     at com.acta.adapter.sdk.StreamOperationWrapper.beginStream(StreamOperationWrapper.java:88)
     at com.acta.adapter.sdk.AdapterRunnerImpl.processBeginOperation(AdapterRunnerImpl.java:1762)
     at com.acta.adapter.sdk.AdapterServiceDataListener.handleBrokerMessage(AdapterServiceDataListener.java:90)
     at com.acta.brokerclient.BrokerClient.handleMessage(BrokerClient.java:439)
     at com.acta.brokerclient.BrokerClient.access$100(BrokerClient.java:53)
     at com.acta.brokerclient.BrokerClient$MessageHandler.run(BrokerClient.java:1621)
     at com.acta.brokerclient.ThreadPool$PoolThread.run(ThreadPool.java:100)

As Jay mentioned above it might be due to the size of the Excel spreadsheet as you might be hitting the limitation in Apache POI library used for adapter.
What is the size of the Excel file?
What is the value of -Xmx parameter - see DS Management Console > Adapter configuration page.
Thank you,
Viacheslav.

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/

Java heap space error in obiee 10g

Dear All,
We are unable to generate the reports. We observed the following error in OC4J
12/06/06 17:43:28 java.lang.OutOfMemoryError: Java heap space
12/06/06 17:43:36 Exception in thread "Timer-8" Exception in thread "Timer-0" j
va.lang. OutOfMemoryError: Java heap space
12/06/06 17:44:45 java.lang.OutOfMemoryError: Java heap space
12/06/06 17:45:18 java.lang.OutOfMemoryError: Java heap space
12/06/06 17:45:19 java.lang.OutOfMemoryError: Java heap space
12/06/06 17:45:26 java.lang.OutOfMemoryError: Java heap space
How to resolve this.
Thanks.

Hi,
Increase the heap size by setting -Xmx to the desired amount of memory in the <java-option> element in opmn.xml:
<module-data> <category id="start-parameters">
<data id="java-options" value="-Xmx256M" />
</category>
</module-data>
Alternatively, you can set a system property at OC4J startup:
java -Xmx256M -jar oc4j.jar
Refer : http://docs.oracle.com/cd/B14099_15/web.1012/b14011/diagnosis.htm
Regards,
Srikanth

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

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

OracleAS: java.lang.OutOfMemoryError: Java heap space

Hi all,
Now I'm using Oracle AS 10.1.3.0, and after some hours, the error "java.lang.OutOfMemoryError: Java heap space" appeared.
And this is the information of OracleAS memory when it has error:
Memory MXBean
Heap Memory Usage: init = 268,435,456(262,144K) used = 112,462,248(109,826K) committed = 396,558,336(387,264K) max = 517,013,504(504,896K)
Non-Heap Memory Usage: init = 16,973,824(16,576K) used = 98,829,840(96,513K) committed = 99,319,808(96992K) max = 167,772,160(163,840K)
Memory Pool MXBeans
Code Cache
Type: Non-heap memory
Usage: init = 196608(192K) used = 27540032(26894K) committed = 27885568(27232K) max = 33554432(32768K)
Peak Usage: init = 196608(192K) used = 27556992(26911K) committed = 27885568(27232K) max = 33554432(32768K)
PS Eden Space
Type:Heap memory
Usage:init = 22478848(21952K) used = 26278816(25662K) committed = 50069504(48896K) max = 54722560(53440K)
Peak Usage: init = 22478848(21952K) used = 57802752(56448K) committed = 57802752(56448K) max = 58589184(57216K)
Collection Usage:init = 22478848(21952K) used = 0(0K) committed = 50069504(48896K) max = 54722560(53440K)
PS Survivor Space
Type: Heap memory
Usage: init = 3670016(3584K) used = 1082080(1056K) committed = 2424832(2368K) max = 2424832(2368K)
Peak Usage: init = 3670016(3584K) used = 19857256(19391K) committed = 19857408(19392K) max = 19857408(19392K)
Collection Usage: init = 3670016(3584K) used = 1082080(1056K) committed = 2424832(2368K) max = 2424832(2368K)
PS Old Gen
Type: Heap memory
Usage: init = 238616576(233024K) used = 85108712(83113K) committed = 344064000(336000K) max = 477233152(466048K)
Peak Usage: init = 238616576(233024K) used = 477233152(466048K) committed = 477233152(466048K) max = 477233152(466048K)
Collection Usage: init = 238616576(233024K) used = 85108712(83113K) committed = 344064000(336000K) max = 477233152(466048K)
PS Perm Gen
Type: Non-heap memory
Usage: init = 16777216(16384K) used = 71289808(69618K) committed = 71434240(69760K) max = 134217728(131072K)
Peak Usage: init = 16777216(16384K) used = 71289808(69618K) committed = 71696384(70016K) max = 134217728(131072K)
Collection Usage: init = 16777216(16384K) used = 71177496(69509K) committed = 71434240(69760K) max = 134217728(131072K)
And this is runtime prarameter:
-Xrs -server -XX:MaxPermSize=128m -Xms256m -Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false
Any one can help me?
Rgds.

Think about what happens in your program. If your program loads lots of data into memory of the AS (=heap) and you have lots of users, then you can get errors like this. The obvious solution is to start raising the heapsize, but you cannot do that anymore, since you're out of physical memory.
So with the information I have seen so far, in this case you either have to buy more memory, get less users or refactor your program.

WEBLOGIC - java.lang.OutOfMemoryError: Java heap space

hi,
i am using Weblogic 10.3 in production mode
We are getting error " java.lang.OutOfMemoryError: Java heap space " frequently , and
we are using the default args
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=512m
OS - > Windows Server 2003
please help
Regards
Jeethi George

Hi George,
The Setting you have provided is wrong ...that is the reason you are getting OutOfMemory in Heap.
Your Setting is (As you have mentioned in your very first post): JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=512m
Just a Bit Explaination:
Formula:
(OS Level)Process Size = [ Java Heap (+) Native Space (+) (2-3% OS related Memory) ]
PermSize : It's a Netive Memory Area Outside of the Heap, Where ClassLoading kind of things happens. In an operating System like Windows Default Process Size is 2GB (2048MB) default (It doesnt matter How much RAM do u have 2GB or 4GB or more)...until we dont change it by setting OS level parameter to increase the process size..Usually in OS like Solaris/Linux we get 4GB process size as well.
Now Lets take the default Process Size=2GB (Windows), Now As you have set the -Xmx512M, we can assume that rest of the memory 1536 Mb is available for Native codes.
(ProcessSize - HeapSize) = [Native (+) (2-3% OS related Memory)]
2048 MB - 512 MB = 1536 MB
THUMB RULES:+
MaxPermSize = (MaxHeapSize/3) ----Very Special Cases
MaxPermSize = (MaxHeapSize/4) ----Recommended
In your Case -Xmx and -XX:MaxPermSize bith are same ....That is the reason you are getting the OutOfMemory Error in Heap.
We should increase/tune the MaxPermSize when we deploy a very large application (like a WebApplication which uses many JSPs, or PageFlows/Portal framework etc.) in our Server.
What should be the exact setting of these parameters depends on the Environment /Applications etc...
But Just try -Xmx1024m -Xms1024m -XX:MaxPermSize256m
Another recommendation for fine tuning always keep (Xmx MaxHeapSize & Xms InitialHeapSize same).
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

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

Oracle WebLogic 10.0 MP2 Installation error: Java Heap Space

Similar Messages

Maybe you are looking for