Windchill on AIX heapdump and Javacore issues

Windchill on AIX heapdump and Javacore issues

Windchill system, the main reason for dump and javacore is memory overflow, in general, Methodserver and Tomcat memory settings on the small, many concurrent users will cause memory overflow, this situation as long as the configuration can be modified , and the server configuration has reached the bottleneck, only upgrade the server's hardware configuration, it is recommended that the configuration is 1 CPU needs 4G of memory, and another is because the customized code is not standard, did not release resources, resulting in memory accumulation, this situation as long as the restart Windchill service is normal, Need to track code, more difficult.

Did you install an IBM JVM service in Aix? Like Weblogic,websphere?
This type of file is typically generated when the IBM JVM crashes or when JVM memory overflows.
What version of your JDK is.
Here are some of the solutions IBM has given to WebSphere and different versions of JDK, and you can refer to:
An IBM JDK V1.3.1 SR5 version
To assist in capturing error messages for the first time, starting with the IBM JDK V1.3.1 SR5 (131-20030618), the system automatically generates Heapdumps and Javacores when the Java heap space runs out. If you want to not automatically generate Heapdumps and javacores when the Java heap space is depleted, follow these steps:
For was 4.0.x:
1. Locate the <was_home>/bin/startupserver.sh (. bat) file, where <WAS_HOME> represents the installation directory of was
2. Open the file with a text editor and add the following 2 lines at the top of the file:
UNIX Platform:
Export Ibm_heapdump_outofmemory=false
Export Ibm_javadump_outofmemory=false
Window Platform:
Set Ibm_heapdump_outofmemory=false
Set Ibm_javadump_outofmemory=false
3. Save and close the file, reboot was
For was 5.0.x or 5.1.x:
1. Open the admin console and select: Server > Application Server > Server name to be changed > process definition > Environment entry
2. Create the following 2 entries:
Name Value
Ibm_heapdump_outofmemory false
Ibm_javadump_outofmemory false
3. Save configuration changes, reboot was
Two IBM java SDK 1.4.2 SR5
Starting with the Java SDK 1.4.2 SR5, with regard to generating heapdump and Javacore, a new feature is introduced to prevent system-generated heapdump and Javacore from automatically generating operating system file system space, so that in the Java SDK 1.4.2 In SR5 and later versions, Heapdump and Javacore files will not be generated when the kill-3 is used.
This new feature allows you to set options to control the maximum number of heapdump and Javacore files generated by the Java process when the corresponding signal is received. To use this new feature, you need to first set the following variables in the operating system environment:
Export java_dump_opts= "onanysignal (Javadump[n],heapdump[m])"
where n is the maximum number of Javacore generated, M is the maximum number of heapdump generated.
When this variable is set, the Java process generates the Heapdump and Javacore files when it receives the kill-3 (or other signals), and the maximum number of files equals the values of M and N in the option, and the values of M and n can be set according to the actual requirements.
For example:
Before you start WebSphere, set the following environment variables:
Export java_dump_opts= "onanysignal (javadump[5],heapdump[5])"
This will generate a maximum of 5 heapdump and Javacore when the corresponding signal is received, and no further heapdump and Javacore files will be generated.
Attention:
If you set the Ibm_heapdump=true variable, an extra Heapdump file will be generated so that the Heapdump file will be n+1, which is avoided in the Java SDK 1.4.2 SR7.
If none of the above 2 methods are resolved, the following 2 recommendations
1 to the IBM official website query whether there are other solutions, the following is the Web site
Http://www-900.ibm.com/cn/support/viewdoc/knowledgebase
2 Add hardware memory or modify code.