| Summary: | OutOfMemoryError while xpath analysis for 11K rules using IBMJDK 1.5 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Praful Rajawat <prafulr> | ||||||
| Component: | TPTP | Assignee: | Eugene Chan <ewchan> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | blocker | ||||||||
| Priority: | P3 | CC: | apnan, labadie, zung | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | |||||||||
| Bug Blocks: | 141647 | ||||||||
| Attachments: |
|
||||||||
|
Description
Praful Rajawat
cc Sorry, I meen IBM JDK 1.5 :-) Praful, according to the trace stack you provided. 'jre14' is detected and used. Would you also provide the access.log and symptom catalog to reproduce the problem. This problem also in tptp.sdk-TPTP-4.2.1-200608041327.zip From the trace you can see I have used IBM JDK 1.5 java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20060504 (JIT enabled) May be JRE detection is not correct. Eugene, it's OK to use the org.eclipse.tptp.platform.provisional.jre14.fastxpath.FastXPathEngine for IBM JRE 5 because both IBM JREs 1.4.2 and 5 are using the same org.apache.XPathAPI. Sun is using in JDK 5 a different XPathAPI and not the Apache one. Thanks Alex for your information. Praful, does the problem happen in a particual JVM or it's also happening in JVM other than IBM JDK 1.5? IBM/SUN/1.4.2/1.5? Thanks. It works in IBM JDK 1.4.2. I have not tested this in SUN JVN Created attachment 48713 [details]
Patch
Please test the attached patch that seems to solve the OutOfMemoryError.
Thanks Alex, the patch you provided is reviewed and smoketested. It solves the memory leak problem in the code. I have tested the patch on IBM 1.4.2, IBM 5, SUN 1.4.2 and SUN 5 and all pass using -Xms256m and -Xmx512m Here are the performance measurement from the different JVM. -20000 cbe events, 11600 symotom definitions, analysis one event 3 times java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cndev-20040511 (JIT ena bled: jitc)) !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=206627 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=1081 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=641 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=641 IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows 2000 x86-32 j9vmwi3223-20060 817a (JIT enabled) J9VM - 20060816_07652_lHdSMR JIT - 20060816_2032_r8 GC - 20060815_AA) JCL - 20060817 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=362511 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=831 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=651 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=501 java version "1.4.2_11" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_11-b06) Java HotSpot(TM) Client VM (build 1.4.2_11-b06, mixed mode) !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=164637 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=712 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=620 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=631 java version "1.5.0_08" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03) Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing) !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=150747 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=731 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=621 !MESSAGE ExtendedAnalyze.run - org.eclipse.tptp.symptom.analysis.XPathAnalysisOperation: deltaTime=661 Created attachment 48739 [details]
updated patch
Update component. fixed in 4.2.1 and HEAD The OOM exception is thrown due to the fact that maximum number of classloader is reached. For historical reasons the J9 JVM imposes an artificial limit on the maximum number of classloaders that an application can create. To workaround the problem without the fix posted here(for earlier drivers), user can adjust the value with JVM argument -Xmxcl. -Xmxcl16384 should also work around the problem reported here. Closed |