Java heap dump location

Hi Everyone.
How do I configure where I can output the java heap dumps?
Right now they're dumped in /tmp automatically.
Thanks

Hi Khaled,
It depends on what is the operating system and the jdk. For sun jdk:
-XX:HeapDumpPath=<directory where to save the heap dumps>
for IBM:
BM_HEAPDUMPDIR environment variable should be set to point to the desired location.
Greetings, Myriana

Similar Messages

IBM Heap Dump command line utilities

Hello,
I am looking for command line parameter for IBM Heap dump location in configtool. I know we can set using environment variable IBM_HEAPDUMPDIR but I would like to get some command utilities to set it in configtool.
Thanks in Advance !

Hi,
The JVM checks each of the following locations for existence and write-permission, then stores the Heapdump in the first one that is available.
The location that is specified using the file suboption on the triggered -Xdump:heap agent.
The location that is specified by the IBM_HEAPDUMPDIR environment variable, if set (_CEE_DMPTARG on z/OS(R)).
The current working directory of the JVM processes.
The location that is specified by the TMPDIR environment variable, if set.
The /tmp directory. On Windows(R), C:\temp.
Details : http://publib.boulder.ibm.com/infocenter/javasdk/v1r4m2/index.jsp?topic=/com.ibm.java.doc.diagnostics.142j9/html/contents.html
Regards,
Sandeep

AD4J: Unable to start Heap Dump due to OS Error

When Java 'Heap Dump' is requested, the following message is shown:
Unable to start Heap Dump due to OS Error.
Details of the monitored JDK and application server are given below:
JDK: Sun JDK 1.4.2_08 on Solaris 9
Application Server: WebLogic 8.1 SP4
1. What could be the possible cause? No errors are logged in jamserv/logs/error_log. Is there any way to enable detailed logging?
2. Each time the heap dump is requested, a file of the format heapdump<n> gets created in /tmp (e.g. /tmp/heapdump12.txt). If you see the file, it contains the following:
a) a line containing summary of the heap usage, and
b) stack traces of all the threads
Thanks!

Wrong Forum?

Java 1.4.2. - full heap dump?

Hello,
Is there any possibility to generate full heap dump (core dump) in java 1.4.2. on demand?
Best regards,
Peter

If you are in Unix platform, you can use this script to have thread dump.
I am not sure whether you can generate coredump with out an application crash .
kill -3 <java pid> will provide full stacktrace of the java process thread dump.
Note: kill -3 will not terminate the java process, it will only generate full stacktrace in your log file and safe to use while the java process is running.
you can get the java process id, using this unix cmd "ps -ef | grep java" .
#!/bin/ksh
[ $# -le 0 ] && echo "USAGE: $0 <pid>" && exit
for i in 1 2
do
DT=`date +%Y%m%d_%H%M`
prstat -Lmp $1 1 1 >> prstat_Lmp_$i_$DT.dmp
pstack $1 >> pstack_$i_$DT.dmp
kill -3 $1
echo "prstat, pstack, and thread dump done. #" $i
sleep 1
echo "Done sleeping."
done
Pls go through some of this links, this will provide you on how to debug the issue with the logs generated by the scripts:
http://support.bea.com/application_content/product_portlets/support_patterns/wls/UnexpectedHighCPUUsageWithWLSPattern.html
http://www.unixville.com/~moazam/stories/2004/05/18/debuggingHangsInTheJvm.html

Heap dumps again & again ...

Hi,
I'm looking into an application which is frequently facing heap dumps... I have an idea where the problem occurs ... Trouble is I cannot run the app from on my local m/c due to some issue.... I've tried HeapAnalyser on the dump file & results show a huge collection of primitive objects & java.lang.Objects ... But I don't see any place where the trouble's occuring... Is there a way I can analyse the code better ?? How can we go about solving the problem of heap dump (w/o having to increase memory allocated to it)?

Hi ,
App Server: WAS 5.0 & heap size's 512 MB ... Looking at the log java.io.OutOfMemory error occurs only when some changes done to the profile of a user is activated by owner .... & this is a place when max data is fetched from DB & attempted to be stored into Vector object ...
I'm currently going to use checkpoints at various locations to log mem usage... Any better suggestion ?

Heap dump file - Generate to a different folder

Hello,
When the AS Java iis generating the heap dump file, is it possible to generate it to a different folder rather than the standard one: /usr/sap// ?
Best regards,
Gonçalo Mouro Vaz

Hello Gonçalo
I don't think this is possible.
As per SAP Note 1004255;
On the first occurrence (only) of an OutOfMemoryError the JVM
will write a heap dump in the
/usr/sap/ directory
Can i ask why you would like it in a different folder?
Is it a space issue?
Thanks
Kenny

Problems with creation of an HEAP Dump

Dear all,
I have tried to create a HEAP Dump (CntrBreak) with the Java-based SAPMC Console (Process Table => server<no.> => DumpStack, but I get no dump on operation system (/usr/sap/<SID>/JC01/j2ee/cluster/server0/). I set the parameter -XX:HeapDumpOnOutOfMemoryError -XX:HeapDumpOnCtrlBreak in the VM. Our Java version is 1.4.12, the OS is Sun Solaris.
Did anyone know why it not functioned in our solution?
Many thanks in advanced.
Patrick

Hi,
The Java based MC should provide the same functionality as the MMC. I tested today to trigger a heap dump as you have described and I had success.
As the "Dump Stack" action is a protected one, the user should be asked for user/pass. Is it also for you so?
And I have found several notes describing problems with the authentication of the sapstartsrv user on different unix platforms. As there is no action at all logged in your case, I guess that this could be the problem.
Here are the notes I found:
[Note 927637 - Web service authentication in sapstartsrv as of Release 7.00|https://service.sap.com/sap/support/notes/927637]
[Note 992907 - sapstartsrv user authentication on Solaris|https://service.sap.com/sap/support/notes/992907]
I hope this helps.
Have you tried already to perform the action from an MMC?
Regards,
Krum

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.

Heap Dump file generation problem

Hi,
I've configured configtool to have these 2 parameters:
-XX:+HeapDumpOnOutOfMemoryError
-XX:+HeapDumpOnCtrlBreak
In my understanding, with these 2 parameters, the heap dump files will only be generated under 2 situations, ie, when out of memory occurred, or user manually click CLTR + BREAK in MMC.
1) Unfortunately, there are many heap dump files (9 in total) generated when none of the above situation occured. I couldnt find "OutOfMemoryError" in the default trace, nor the shallow heap size of those heap dump files are anywhere near the memory limit. The consequences are our server run out of disk space.
My question is, what are the other possibilities that heap dump file will be generated?
2) In the Memory Consumption graph (NWA (http://host:port/nwa) -> System Management -> Monitoring -> Java Systems Reports), out of memory error occurred when the memory usage is reaching about 80% of the allocated memory. What are the remaining 20% or so reserved for ?
Any help would be much appreciated.
Thanks.

Hi,
Having the -XX:+HeapDumpOnCtrlBreak option makes the VM trigger a heap dump, whenever a CTRL_BREAK event appears. The same event is used also to trigger a thread dump, an action you can do manually from the SAP Management Console, I think it is called "Dump stacks". So if there was someone triggering thread dumps for analysis of other types of problems, this has the side effect of writing also a heap dump.
Additionally, the server itself may trigger a thread dump (and by this also a heap dump if the option is present). It does this for example when a timeout appears during the start or stop of the server. A thread dump from such a moment allows us to see for example which service is unable to start.
Therefore, I would recommend that you leave only the -XX:+HeapDumpOnOutOfMemoryError, as long as you don't plan to trigger any heap dumps on your own. The latter will cause the VM to write a heap dump only once - on the first appearance of an OutOfMemoryError.
In case you need to trigger the heap dumps manually, leave the -XX:+HeapDumpOnCtrlBreak option for the moment of troubleshooting, but consider if you want to keep it afterwards.
If heap dumps were written because of an OutOfMemoryError you should be able to see this in the dev_server file in /usr/sap/<SID>/<inst>/work/ . Also there you should be able to see if indeed thread dumps were triggered (just search for "Full Thread ").
I hope this helps.
Regards,
Krum

Wily Introscope Enterprise Manager fails to start due to Java Heap

Hello All,
I just installed Wily Introscope for the first time. I have successfully installed it from the log below:
Summary
Installation: Successfulwith errors.
396 Successes
0 Warnings
1 NonFatalErrors
0 FatalErrors
I also confirm that the Introscope Enterprise Manager is started as a service.
However, when i try to launch enterprise by following the path All Programs > CA Wily > Introscope 8.2.3.5 > Introscope Enterprise Manager....
I get the error below:
3/29/11 07:11:46 PM PDT [ERROR] [Manager.Bootstrap] Load all Management Modules FAILED.
3/29/11 07:11:46 PM PDT [ERROR] [Manager] The EM failed to start. Java heap space
I have also adapted my Java Heap from 512 to 1024 in EMService.conf file but I still get same error. This was the recommendation in this related forum post - Wily Introscope - EM failed to start
Please help!!!!

Hello,
Like I said, I have increased the value to 1024MB and still not starting.
The corresponding section of the EMService is pasted below:
Wrapper Properties
Java Application
wrapper.java.command=jre
bin
java.exe
wrapper.working.dir=.\
Java Main class
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
Java Classpath (include wrapper.jar) Add class path elements as
needed starting from 1
wrapper.native_library=ServiceWrapper32
wrapper.java.classpath.1=./lib/ServiceWrapper32.jar
wrapper.java.classpath.2=./launcher.jar
#wrapper.java.classpath.3=
Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=./lib
Java Additional Parameters
Note: On 64-bit Windows only, the first additional parameter must be: -Xrs
#wrapper.java.additional.1=
wrapper.java.additional.1=-Xrs
wrapper.java.additional.2=-Djava.awt.headless=false
Initial Java Heap Size (in MB)
wrapper.java.initmemory=512
Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=1024
Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=org.eclipse.core.launcher.Main
wrapper.app.parameter.2=-consolelog
wrapper.app.parameter.3=-noExit
wrapper.app.parameter.4=-product
wrapper.app.parameter.5=com.wily.introscope.em.product
wrapper.app.parameter.6=-install
wrapper.app.parameter.7=./product/enterprisemanager
wrapper.app.parameter.8=-configuration
wrapper.app.parameter.9=./product/enterprisemanager/configuration
Number of seconds to allow between the time that the Wrapper launches
the JVM process and the time that the JVM side of the Wrapper responds
that the application has started. 0 means never time out. Defaults to 30 seconds.
wrapper.startup.timeout=300
Please help

JVMPI_GC_ROOT_MONITOR_USED - what does this mean in a heap dump?

I'm having some OutOfMemory errors in my application, so I turned on a profiler, and took a heap dump before and after an operation that is blowing up the memory.
What changes after the operation is that I get an enormous amount of data that is reported under the node JVMPI_GC_ROOT_MONITOR_USED. This includes some Oracle PreparedStatements which are holding a lot of data.
I tried researching the meaning of JVMPI_GC_ROOT_MONITOR_USED, but found little help. Should this be objects that are ready for garbage collection? If so, they are not being garbage collected, but I'm getting OutOfMemoryError instead (I thought the JVM was supposed to guarantee GC would be run before OutOfMemory occurred).
Any help on how to interpret what it means for objects to be reported under JVMPI_GC_ROOT_MONITOR_USED and any ways to eliminate those objects, will be greatly appreciated!
Thanks

I tried researching the meaning of
JVMPI_GC_ROOT_MONITOR_USED, but found little help.
Should this be objects that are ready for garbage
collection? Disclaimer: I haven't written code to use JVMPI, so anything here is speculation.
However, after reading this: http://java.sun.com/j2se/1.4.2/docs/guide/jvmpi/jvmpi.html
It appears that the "ROOT" flags in a level-2 dump are used with objects that are considered a "root reference" for GC (those references that are undeniably alive). Most descriptions of "roots" are static class members and variables in a stack frame. My interpretation of this doc is that objects used in a synchonize() statement are also considered roots, at least for the life of the synchronized block (makes a lot of sense when you think about it).

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

Pages failing with Java Heap errors

We are running CF 8,0,0,176276 on a Windows 32 bit 2003
server, with IIS 6 and Java Runtime version 6 ( it's really version
1.06).
We started getting the java heap error messages two weeks
ago. Now we are also getting the 'GC overhead limit exceeded'
error, which is concerned with the Java garbage collection. I tried
to change the JVM heap size from 1GB to 2GB, but CF wouldn't start
up. I've since found out that Windows 32bit servers can't use 2GB
for Java.
One java article I found said to turn off the Java garbage
collection using -XX:-UseGCOverheadLimit (
http://forums.java.net/jive/message.jspa?messageID=228596).
It seems like turning off the garbage collection would be the
opposite of what I am trying to do. Are there any thoughts about
this?
Are there any hotfixes for CF8? and where are they located?
Scott

Scott, the error is a symptom, not the cause of your
problems. Turning off that option won't "solve" the problem, which
is that you're running out of memory. More on that option in a
moment.
Let's talk first about your observation of trying to change
the max memory from 1 to 2 gig. Since you're on Windows (32 bit),
as you say, you can't use more than 2g per process (it's not really
a Java limit, but rather a Windows one).
But as you found, you can't set CF to 2g because the JVM
won't start. Again, this is not a CF-specific issue. You can see
discussions of the same problem with plain old Java apps, as at
http://forums.java.net/jive/message.jspa?messageID=228596.
So, similar to what they say, the consensus seems to be that
you can set it to somewhere between1.3 and 1.7 gb, before the JVM
won't start. You have to try different values for yourself.
Now, that extra few hundred meg may be all you need to get
past your problem, but really that's often just forestalling the
inevitable. You need to find why CF is using so much memory. You
say you're using CF8 but don't say if it's Enterprise or Standard.
If the former, then you have the CF8 Server Monitor (accessible in
the CF Admin, and discussed in a multipart series I wrote for the
Adobe Dev Center, as discussed at
http://carehart.org/blog/client/index.cfm/2008/7/30/45page_server_monitor_guide).
That, as well as tools like FusionReactor and SeeFusion, can help
you to better see how CF is using memory.
All three offer a graphical interface to show how memory use
is trending. You may see if it grows steadily throughout the day,
or grows in spikes. People tend to say "I have a memory leak", when
in fact it may be just that they have either a few requests that
use too much memory (so you'll see a stair stepping rise in memory
use concurrent with their execution), or it may be that they're
sticking stuff into shared scopes (session, application, or server)
and those are living well beyond the live of each request.
The CF8 Server Monitor even has a memory tracking feature,
but it has to be used carefully. If you enable it, you may find it
brings your server to its knees.I'll do a blog entry soon on how to
use it most effectively (something I learned since writing the
articles last year).
One thing that the monitor can tell you, without any of the
"start" buttons enabled at the top of the monitor, is how many
sessions you have. That may be very enlightening. You may have
thousands of them, and not realize it, because of bots, spiders,
and other crap requests. See the "active sessions" page of the
Server Monitor, and its graph icon in particular (discussed in more
detail in one of my articles).
Sadly, neither FusionReactor nor SeeFusion can tell you how
many sessions are currently running, so if you're on CF8 Standard
(or if others reading this are on 6 or 7, where they can use FR or
SF), you can't easily see how many sessions there are. (There are
undocumented, unsupported methods, such as discussed at
http://rewindlife.com/2003/09/08/undocumented-application-scope-functions/.
Just be aware some techniques work differently depending on whether
J2EE sessions are enabled in th CF admin.)
Finally, about your observation of the usegcoverheadlimit
option, and the recommendation to turn it off: the article you
point to doesn't say doing so would disable GC. I'm curious how you
may have concluded that.But digging into things more, I see that
disabling it (using the - before it) will turn off a feature
(introduced in 6) which limits the proportion of the VM's time that
is spent in GC before an OutOfMemory error is thrown. That's the
error you're seeing, that the JVM has detected too much time is
being spent in doing GC.
So turning off the option doesn't "turn off the Java garbage
collection". It just changes whether an OOM error will be thrown
even before being really out of memory, simply because too much
time is being spent in GC.
And even then, how this option works (if enabled, which it is
by default) changes depending on whether you're using a parrallel
or concurrent collector (as discussed in two places in
http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html,
if you search for that switch).
Hope some of that helps.

Hprof heap dump not being written to specified file

I am running with the following
-Xrunhprof:heap=all,format=b,file=/tmp/englog.txt (java 1.2.2_10)
When I start the appserver, the file /tmp/englog1.txt gets created, but
when I do a kill -3 pid on the .kjs process, nothing else is being written to
/tmp/englog1.txt. In the kjs log I do see the "Dumping java heap..." message
and a core file is generated.
Any ideas on why I'm not getting anything else written to /tmp/englog1.txt?
Thanks.

Hi
It seems that the option you are using is correct. I may modify it to something like
java -Xrunhprof:heap=all,format=a,cpu=samples,file=/tmp/englog.txt,doe=n ClassFile
This seems to work on 1.3.1_02, so may be something specific to the JDK version that
you are using. Try a later version just to make sure.
-Manish

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

Java heap dump location

Similar Messages

Maybe you are looking for