[ http://issues.apache.org/jira/browse/XALANJ-1986?page=all ]
Brian Minchau updated XALANJ-1986:
----------------------------------
Fix Version: 2.7
> Core dump: Sun Hotspot JVM 1.3.1_11b-02 optimizer core dumps optimizing a
> Xalan method
> ---------------------------------------------------------------------------------------
>
> Key: XALANJ-1986
> URL: http://issues.apache.org/jira/browse/XALANJ-1986
> Project: XalanJ2
> Type: Bug
> Components: Xalan-extensions, Xalan, transformation
> Versions: 2.4Dx
> Environment: Sun Sparc Workstation Netra-T4, Solaris 5.9, Sun Hotspot JVM
> 1.3.1_11-b02 (Optimization ON), BEA Weblogic 7.0 SP4 running Java Webapps (no
> JNI/native code), XalanJ2 (Implementation version 2.4.D1)
> Reporter: Manish D Jani
> Priority: Blocker
> Fix For: 2.7
>
> Problem:
> We have four systems each configured as specified above in the Environment
> section. Since the last few weeks, except for one, the rest of the 3 systems
> are dumping core averaging at one per day.
> On Sun's advise, we have enabled the -XX:+PrintCompilation option for the
> JVM. For every core dump now, we see one or the other Xalan method's being
> called immediately before the system dumps core. Below are the methods we
> have come across so far:
> org.apache.xalan.extensions.MethodResolver::getMethod
> org.apache.xalan.transformer.ResultTreeHandler::sendEndPrefixMappings
> org.apache.xalan.transformer.ResultTreeHandler::flushPending
> org.apache.xalan.extensions.ExtensionHandlerJavaClass::callFunction
> In some of the core dumps, we have seen the JVM crash when in the append()
> and the toUpperCase() methods.
> On Sun's advise, so far we have excluded the
> org.apache.xalan.extensions.MethodResolver::getMethod &
> org.apache.xalan.transformer.ResultTreeHandler::sendEndPrefixMappings from
> the Hotspot optimizations. After exclusion, none of the core dumps have
> displayed these methods in compilation immediately prior to the core dumps.
> Are there threading issues or any known issues in the use of extensions or
> transformers that could bring down the JVM Hotspot JIT optimizer to core dump?
> Xalan version (Manifest file):
> ==============================
> Manifest-Version: 1.0^M
> Main-Class: org.apache.xalan.xslt.Process^M
> Created-By: 1.2.2 (Sun Microsystems Inc.)^M
> Class-Path: jaxp.jar xercesImpl.jar crimson.jar xml-apis.jar^M
> ^M
> Name: org/apache/xml^M
> Implementation-Vendor: Apache Software Foundation^M
> Implementation-URL: http://xml.apache.org/xalan-j/dist/^M
> Implementation-Version: 2.4.D1^M
> Implementation-Title: org.apache.xml^M
> Comment: DTM implementation and utilities^M
> ^M
> Name: org/apache/xpath^M
> Implementation-Vendor: Apache Software Foundation^M
> Implementation-URL: http://xml.apache.org/xalan-j/dist/^M
> Implementation-Version: 2.4.D1^M
> Implementation-Title: org.apache.xpath^M
> Comment: XPath engine^M
> ^M
> Name: org/apache/xalan^M
> Specification-Title: Java API for XML Processing^M
> Specification-Vendor: Sun Microsystems Inc.^M
> Implementation-Vendor: Apache Software Foundation^M
> Implementation-URL: http://xml.apache.org/xalan-j/dist/^M
> Specification-Version: 1.1^M
> Implementation-Version: 2.4.D1^M
> Implementation-Title: org.apache.xalan^M
> Comment: Main Xalan engine implementing TrAX/JAXP^M
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
