Solaris 10 - Zones - Java Heap Allocation

I have a SUN T5240 running Solaris 10 with 2 zones configured.
We have 64GB of RAM on board....
I am unable to start any of my JAVA applications/methods with more than 1280mb of java heap allocated.
ulimit -a shows:
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
coredump(blocks) 0
nofiles(descriptors) 256
vmemory(kbytes) unlimited
Can anyone tell me why I can't get to the RAM/memory that I know is there?
Thanks

soularis wrote:
We're only asking for Xmx2048 currently and we are still being denied...I need to run in 32bit mode for my application.what are you running in 32 bits? solaris? java? or are you locked in a 32 bit zone on a 64bit server? I'm not even sure
SPARC is supported in 32 bit mode anymore (for solaris, anyway).
example:
java -Xmx2g -version
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Seems like I should be able get 2GB in 32bit Solaris 10
Right?one would think. Though you should make sure that whatever you are using is allocated enough swap to run. It's possible that you are running in a constrained zone, so even if the machine has 64G, your zone is only allocated a small portion of that.
Heres the 64bit attempt:
# java -d64 -Xmx2048m -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_14-b03, mixed mode)This under the same user? Odd that 64 bits starts up, but 32 bits doesn't. You also might try and upgrade to 1.5.0_18 - it might be a bug that was introduced and now fixed.

Similar Messages

SAP Java and Solaris Zones SolMan 4.0

May require Solaris Zones experience to continue.
I have three SAP database instances/central instances running in three sparse Solaris zones with no problem.
I have created a new sparse zone for a new SAP installation (Solution Manager 4.0) and started the installation. SAP requires a 1.4.2 SDK even though Java 1.5 comes with Solaris 10. The 1.4.2 SDK is in /usr/j2se. The installation in the sparse zone errors out because it can't get "write" rights to /usr/j2se/jre/lib/security/local_policy.jar as it is trying to install some security encryption JCE component.
I have thought about creating a /usr/j2se_zonename file system, copying the contents of /usr/j2se into it and then mounting /usr/j2se_zonename in the zone as a lofs with the name /usr/j2se. However when I do the copy of /usr/j2se I get some recursion errors.
Any thoughts about how to add a writable /usr/j2se into the sparse zone with the least amount of effort ? Otherwise plan B would be to create a "large" zone with a writable /usr directory.
Received a great answer, that while it may not be architecturally "pure" it may get the job done.
You might just download the relevant JDK tarball and unpack that
somewhere in your zone (anywhere you like), and point SAP at it...
http://java.sun.com/j2se/1.4.2/download.html
Get the one called "self extracting file"-- you can unpack that anywhere
you want.
Message was edited by: Atis Purins

Hi Russ,
no you only have to generate two RFCs to your R/3 and assign them in SMSY to for system monitoring
Then you need a Solution, assign your R/3 to the Solution, setup the system monitoring.
Regards,
uDo

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.

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 heap error

Hi All
I have developed a Matrix report recently and it is throwing error when it was loaded and ran locally and also after registerd in the Apps.The error is "Java Heap Error".Correct me if i am wrong to my knowledge what i am thinking is it is getting time out and unable to process the data.The report is running fine for few number of records.Please help me in this regard.
Help will be really apreciated.
regards,
kalyan

Hi kalyan,
What i know about Java Heap error is, it comes when you exceed the length allocated.
Sometimes it happens that you have to take the whole name upto 59 characters, means if somebody gets beyond the limit of 59, ideally you should truncate it.
If you dont, then it starts giving translation length error or say java heap error.

OutOfMemoryError: Java heap space

Hi There
i am facing som problem in my one of concurrent manager (Output Post Processor) and its showing value of Actual 2 and Target 3 and getting some exception in one of process's log which as follwos.
Exception in thread "PacketReceiver for [172.20.2.11:15028]" java.lang.OutOfMemoryError: Java heap space
     at java.net.SocketInputStream.read(SocketInputStream.java:181)
     at oracle.ias.cache.group.HttpHandler.read(Unknown Source)
     at oracle.ias.cache.group.StreamHandler.read(Unknown Source)
     at oracle.ias.cache.group.EndPoint.read(Unknown Source)
     at oracle.ias.cache.group.PacketReceiver.run(Unknown Source)
Exception in thread "OPPAQMON:206703" java.lang.OutOfMemoryError: Java heap space
     at oracle.jdbc.driver.T4CMAREngine.unmarshalDALC(T4CMAREngine.java:2125)
     at oracle.jdbc.driver.T4C8TTIrxh.unmarshalV10(T4C8TTIrxh.java:119)
     at oracle.jdbc.driver.T4CTTIiov.unmarshalV10(T4CTTIiov.java:188)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:614)
     at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
     at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1225)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
     at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
     at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPAQMonitor.java:429)
     at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:114)
     at java.lang.Thread.run(Thread.java:619)
please help me out how to resolved this issue.
Application: Oracle Ebs-R12(12.1.2)
DB: 11.1.0.7
OS: linux 5*86x64
Waiting for valuable response.
Regards,
Mohsin

Hi Hussein
I have a question on this OPP java heap space .
Let say I have 10 Process allocated for OPP and heap space allocated to OPP is 1024 MB.
Q 1 . Let say 5 requests are running by 5 OPP processes.. Then how this heap memory allocated ?
is it something like heap space / number of running requests by OPP (1024/5 in this case )
Q 2. Let say i have submitted 2 requests . One request needs 800 MB of heap space (based on the past runs )
And Second one requires 500 MB of heap space .
In this we will get java out of memory error ? Am I correct ?
Q 3 . Will all requests after submitted after test case 2 ( Q 2) encounter out of memory errors Since the heap space was exhausted until OPP bounced or full /GC Completed/
Please Correct me if I am wrong
--Thanks In advance.

JAVA HEAP SPACE

dear All
we are running EBS R12 (12.0.6 ) on Sun Solaris 10 on 10.2.0.4 DB. 1 of our custom made report failed with below mentioned error. Its a new report used for first time.
Can anyone tellme how to check the current Java heap space and how to increase it.
INFO: oracle.adf.share.config.ADFConfigFactory No META-INF/adf-config.xml found
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
Regards
Musaddaq

Hi Mussaddaq,
Please refer following as it is discussed below previously:
OutOfMemoryError: Java heap space
https://forums.oracle.com/thread/search.jspa?peopleEnabled=true&userID=&containerType=&container=&q=Java+heap+space
Regards,

OPP JAVA HEAP Out of memory

hi all
ebs:11.5.10.2
db:9i
AIX 5 64-bit
we have 5 target process and 4 actual process
all the actual process are struck and one one is active
and log file of one process out 3 struck is (other 2 logs are same)
[6/20/11 9:12:44 PM] [15905:RT2458306] Starting XML Publisher post-processing action.
[6/20/11 9:12:44 PM] [15905:RT2458306]
Template code: XXXXXXXXXXXXX
Template app: WSH
Language: en
Territory: 00
Output type: PDF
java.lang.OutOfMemoryError
     at oracle.ias.cache.DefaultCacheLogger.flushRecords(Unknown Source)
     at oracle.ias.cache.DefaultCacheLogger.flushBuffer(Unknown Source)
     at oracle.ias.cache.DefaultCacheLogger.flush(Unknown Source)
     at oracle.ias.cache.CacheCleaner.run(Unknown Source)
java.lang.OutOfMemoryError
     at oracle.apps.fnd.cp.opp.OPPRequestThreadManager.checkThreads(OPPRequestThreadManager.java(Compiled Code))
java.lang.OutOfMemoryError
     at oracle.jdbc.driver.LRUStatementCache.addToImplicitCache(LRUStatementCache.java(Compiled Code))
     at oracle.jdbc.driver.OracleConnection.cacheImplicitStatement(OracleConnection.java(Inlined Compiled Code))
     at oracle.jdbc.driver.OraclePreparedStatement.privateClose(OraclePreparedStatement.java(Compiled Code))
     at oracle.jdbc.driver.OraclePreparedStatement.close(OraclePreparedStatement.java(Compiled Code))
     at oracle.jdbc.driver.OracleCallableStatement.close(OracleCallableStatement.java(Compiled Code))
     at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPAQMonitor.java(Compiled Code))
     at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java(Compiled Code))
     at java.lang.Thread.run(Thread.java:570)
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
     at oracle.apps.fnd.common.Pool.createObject(Pool.java(Compiled Code))
     at oracle.apps.fnd.common.Pool.createAvailableObject(Pool.java(Compiled Code))
     at oracle.apps.fnd.common.Pool.resize(Pool.java(Compiled Code))
     at oracle.apps.fnd.common.Pool.run(Pool.java(Compiled Code))
     at java.lang.Thread.run(Thread.java:570)
Exception: java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
     at oracle.ias.cache.group.Sender.run(Unknown Source)
java.lang.OutOfMemoryError
     at oracle.jdbc.dbaccess.DBDataSetImpl._allocItemsAndBuffers(DBDataSetImpl.java(Compiled Code))
     at oracle.jdbc.dbaccess.DBDataSetImpl._allocDataAndItems(DBDataSetImpl.java(Inlined Compiled Code))
     at oracle.jdbc.dbaccess.DBDataSetImpl.setType(DBDataSetImpl.java(Compiled Code))
     at oracle.jdbc.dbaccess.DBDataSetImpl.setType(DBDataSetImpl.java(Compiled Code))
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameterBytes(OracleCallableStatement.java(Compiled Code))
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java(Inlined Compiled Code))
     at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(OracleCallableStatement.java(Compiled Code))
     at oracle.apps.fnd.cp.gsm.GenCartComm.getQueueMessage(GenCartComm.java:186)
     at oracle.apps.fnd.cp.gsf.GSMStateMonitor.waitForNextEvent(GSMStateMonitor.java:95)
     at oracle.apps.fnd.cp.gsf.GSMServiceController.mainLoop(GSMServiceController.java:236)
     at oracle.apps.fnd.cp.gsf.BaseServiceController.run(BaseServiceController.java:71)
     at java.lang.Thread.run(Thread.java:570)
[6/20/11 9:59:51 PM] [UNEXPECTED] [15905:RT2458306] java.lang.reflect.InvocationTargetException
Caused by: java.lang.OutOfMemoryError
     at oracle.xdo.parser.v2.XPathDescendantAxis.getNodeList(XPathAxis.java(Compiled Code))
     at oracle.xdo.parser.v2.XPathStep.evaluate(XPathStep.java(Compiled Code))
     at oracle.xdo.parser.v2.PathExpr.evaluate(XSLNodeSetExpr.java(Compiled Code))
     at oracle.xdo.parser.v2.XSLForEach.processAction(XSLForEach.java(Compiled Code))
     at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java(Compiled Code))
     at oracle.xdo.parser.v2.XSLResultElement.processAction(XSLResultElement.java(Compiled Code))
     at oracle.xdo.parser.v2.XSLNode.processChildren(XSLNode.java(Compiled Code))
     at oracle.xdo.parser.v2.XSLTemplate.processAction(XSLTemplate.java:191)
     at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:508)
     at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:485)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:264)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:150)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:187)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
     at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java(Compiled Code))
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java(Compiled Code))
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:233)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:177)
     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:1657)
     at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:967)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5888)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3438)
     at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3527)
     at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:247)
     at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:157)
[6/20/11 9:59:51 PM] [15905:RT2458306] Completed post-processing actions for request 2458306.
java.lang.OutOfMemoryError
     at java.io.ObjectOutputStream$HandleTable.growSpine(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream$HandleTable.assign(ObjectOutputStream.java(Inlined Compiled Code))
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java(Compiled Code))
     at java.util.Vector.writeObject(Vector.java(Inlined Compiled Code))
     at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
     at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java(Compiled Code))
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java(Inlined Compiled Code))
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code))
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(Compiled Code))
     at oracle.ias.cache.group.StreamHandler.write(Unknown Source)
     at oracle.ias.cache.group.EndPoint.write(Unknown Source)
     at oracle.ias.cache.group.Transport.syncMulticast(Unknown Source)
     at oracle.ias.cache.group.Transport.multicast(Unknown Source)
     at oracle.ias.cache.group.Transport.multicast(Unknown Source)
     at oracle.ias.cache.group.Monitor.ping(Unknown Source)
     at oracle.ias.cache.group.Monitor.run(Unknown Source)
DG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591323.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591369.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591404.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591451.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591486.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591533.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591569.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591614.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591652.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591700.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591734.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591780.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591815.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591861.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591900.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308591946.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMXE003
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308591981.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592027.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592061.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592109.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592143.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592189.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592224.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592270.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592305.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592351.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592385.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592433.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592467.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592513.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592547.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592593.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592628.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/javacore1511652.1308592674.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMDG217: Dump Handler is Processing OutOfMemory - Please Wait.
JVMDG315: JVM Requesting Heap dump file
...........................................JVMDG318: Heap dump file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxxx/heapdump1511652.1308592708.phd
JVMDG303: JVM Requesting Java core file
JVMDG304: Java core file written to /prod/oracle/prodcomn/admin/log/PROD_xxxxx/javacore1511652.1308592755.txt
JVMDG274: Dump Handler has Processed OutOfMemory.
JVMST109: Insufficient space in Javaheap to satisfy allocation request
JVMXE003
JVMST109: Insufficient space in Javaheap to satisfy allocation request
how to get through this error?
Thankz
ApPsMaSti

Please see these MOS docs.
XML Publisher Report Issues [ID 862644.1]
Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError: Java heap space" Error [ID 1268217.1]
Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError" [ID 1266368.1]
OPP Service Log for the 'Create Accounting' process shows 'java.lang.OutOfMemoryError: Java heap space ' Error [ID 1129283.1]
Retro-Notifications Report (Enhanced) - PDF Errors With 'java.lang.OutOfMemoryError' [ID 557898.1]
Costing Summary Rep Errors with Jvmst109: Insufficient Space In Javaheap [ID 391131.1]
Thanks,
Hussein

JVM Java heap space Error || even with -Xms- and -Xmx commands

hi all, i got a problem by allocating a very great boolean array.
first of all, here is my testcode:
public static void main(String[] args) {
          boolean[] testfield = new boolean[70000000];
          while(true){
          //NOP
     }as you see, i try to allocate an array with 70.000.000 boolean values - as 1 boolean may be represented as at least one physical bit we calculate the total amount of needed RAM-Space:
70.000.000 bit / 8 = 8750000 byte
8.750.000 byte = 8.75 MByte
My System ist WinVista Ultimate 64-bit running on a Quadcore T2200 with 2GB-DDR3 RAM
Looking in my Vista Ressourcemanager shows, that eclipse.exe reserves about 1.023 Mbyte....
As IDE I use eclipse
my eclipse.ini looks as follows:
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256M
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms512m
-Xmx1024m
-XX:PermSize=512mby using following VMCommand "-XX:+PrintGCDetails" and running the above code the output displays:
[GC [DefNew: 180K->63K(960K), 0.0008311 secs][Tenured: 43K->107K(4096K), 0.0060371 secs] 180K->107K(5056K), 0.0069249 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
[Full GC [Tenured: 107K->105K(60544K), 0.0044835 secs] 107K->105K(61504K), [Perm : 17K->16K(12288K)], 0.0045553 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
     at termain.main(termain.java:15)
Heap
def new generation   total 4544K, used 163K [0x246a0000, 0x24b80000, 0x24b80000)
eden space 4096K,   4% used [0x246a0000, 0x246c8fe0, 0x24aa0000)
from space 448K,   0% used [0x24aa0000, 0x24aa0000, 0x24b10000)
to   space 448K,   0% used [0x24b10000, 0x24b10000, 0x24b80000)
tenured generation   total 60544K, used 105K [0x24b80000, 0x286a0000, 0x286a0000)
   the space 60544K,   0% used [0x24b80000, 0x24b9a420, 0x24b9a600, 0x286a0000)
compacting perm gen total 12288K, used 16K [0x286a0000, 0x292a0000, 0x2c6a0000)
   the space 12288K,   0% used [0x286a0000, 0x286a41c0, 0x286a4200, 0x292a0000)
    ro space 8192K, 62% used [0x2c6a0000, 0x2cba2ba0, 0x2cba2c00, 0x2cea0000)
    rw space 12288K, 52% used [0x2cea0000, 0x2d4e88e0, 0x2d4e8a00, 0x2daa0000)so can anyone tell me please, how i manage to allocate bigger arrays? or where at least is the problem?
Originally i was thinking like that way: Integer.MAXVALUE = (2^32)-1
=> biggest index an array can have
=> biggest allocation possible with ints weights (((2^32)-^1)/8)/1000*1000 = (round) 537 MByte < 2GByte => everything fine .... but it seems like not :-(
When i try to allocate 60.0000.000 it works fine....but that is far not enough :-&
thank you very much for your helping answers!

The Sun Java virtual machine stores booleans as bytes, not bits, so for an array of 70 million booleans you need 70 million bytes, plus 8 bytes for the object header, and 4 bytes for the array length.
I suspect that your eclipse.ini controls the JVM running the Eclipse IDE, not the JVM running your application. Note that in the -XX:+PrintGCDetails output at the end, it shows you running out of memory with 4MB of young generation and 60MB of old generation. That's the default configuration, as if you hadn't specified -Xms and -Xmx.
The array of 60 million booleans only requires 60 million bytes (plus overhead), which fits in the default old generation.
I think you need to put the -Xms and -Xmx in the same place you put the -XX:+PrintGCDetails, since that does seem to display information about the JVM running your application, not the JVM running Eclipse.

Java heap size adminserver

Hello,
i would like to know the java heap memory size for adminserver by default.
regards
Jean marc

hello,
thanks for your answers.
i install oracle bi publisher in standalone on windows 2008 64 bits.
the installation create a weblogic server with an adminserver, bi publisher is installed in the adminserver.
if i look for setDomainEnv.cmd,
i have
set XMS_SUN_64BIT=256
set XMS_SUN_32BIT=256
set XMX_SUN_64BIT=512
set XMX_SUN_32BIT=512
set XMS_JROCKIT_64BIT=256
set XMS_JROCKIT_32BIT=256
set XMX_JROCKIT_64BIT=512
set XMX_JROCKIT_32BIT=512
so , i use java sun 64 bits , so the setting XMX_SUN_64BIT=512 is used.
but if i look in the task manager, the java.exe process, the memory allocated is around 2G .
i don't find xmx settings in adminserver.log located at
I:\BI_HOME\BI11G2\user_projects\domains\bifoundation_domain\servers\AdminServer\logs
regards
jean marc
Edited by: jmniard on 29 juil. 2011 08:40

OEDQ - Java Heap errors - thoughts?

I came across a rather annoying problem while trying to load data into OEDQ today and wondered if anyone can offer any insight.
2 separate installations (OEDQ 9.0.5) trying to load 2 different data loads (120k records and 35k records) both produced java heap errors while trying to create the datastore connection.
Following the various support articles regarding the java memory settings and systematically "playing" with the various values for min/max and reserved memory setting from dnconfig made no difference, the same java heap error every time.
I then noticed that the 2 data sources were both in the newer .xlsx format having been extracted to excel and then saved, I opened them and re-saved as first .csv and then .xls -- in both cases the data load now worked.
Given that more people will be moving to the newer xlsx format as "default" I wondered if anyone has any ideas on configuration to deal with what appears to be an added overhead when dealing with this format of files? we can of course just tell people not to use it but it would be nice to know why they cant.

Hi,
The current Excel driver works by pulling the whole of the spreadsheet into memory before capturing it. This can mean that with large spreadsheets it is possible not to have enough heap memory allocated to perform this function. This does not normally happen if using server-side data store connections as the server normally has considerably more memory allocated to it than the client application. If you do encounter this and cannot overcome it by adjusting the relevant heap memory settings, the workaround is as as you say to save as a CSV or other text files which can be streamed in (and out).
Probably the reason that xlsx files fail where xls files succeed is that the xlsx save creates a larger file.
Regards,
Mike
Edited by: MikeMatthews on Nov 6, 2012 3:20 AM

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

NetFlow Collector - Java heap space Error

Hello,
I have setup NetFlow colector v6 to receive flows from 3 devices, but today, 4 days after i have started the collector, i receive the folowing error and i'm unable to generate reports anymore:
[2009-01-08 11:13:59 EET] ERROR com.cisco.nfc.report.ReportBuilder - An unexpected error occurred.
java.lang.OutOfMemoryError: Java heap space
I searched on net and it seems that i have to set higher heap space memory for java. Does anybody know how to rezolv this issue on Red Hat?
Red Hat Enterprise Linux ES release 4 (Nahant Update 5)

It seem like that the JVM has run out of all the memory that has been allocated to it. You can change the amount of memory allocated for use by your JVM using the -Xms and -Xmx command line parameters.

Java Heap Space with aRFC Call

Hi,
I got an issue here.
My scenario is : RFC --> PI --> SOAP
PI Version : 7.0
I want to send my material catalog to PI. I have broadly 66 000 Materials. When I send it via RFC call here is my error (SM58 into the SAP HR system):
Java heap space
When I send only one material everything is good
So here is how I send my material :
CALL FUNCTION 'Z3P_MATERIAL_GETLIST'
TABLES
    return = it_return
    RESULT = it_RESULT.
IF p_send = 'X'.
CALL FUNCTION 'Z3P_MATERIAL_GETLIST'
    IN BACKGROUND TASK AS SEPARATE UNIT DESTINATION p_rfc
    TABLES
      return = it_return
      RESULT = it_RESULT.
COMMIT WORK.
ENDIF.
Do I reach the limit of RFC call ? What should I do ?
Thanks

I want to send my material catalog to PI. I have broadly 66 000 Materials. When I send it via RFC call here is my error (SM58 into the SAP HR system):
Java heap space
When I send only one material everything is good :)
For processing a message you are allocated some space and i think that processing 66000 materials at a time you are overshooting this space-limit....however when you are processing only one material it is well within the limit.....
Check these two discussions...it will give you a good insight of what you need to do...
Java Heap size
Re: Using Jco, Good or Bad ?
Regards,
Abhishek.

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

Solaris 10 - Zones - Java Heap Allocation

Similar Messages

Maybe you are looking for