United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-8022548 SPECJVM2008 has errors introduced in 7u40-b34
JDK-8022548 : SPECJVM2008 has errors introduced in 7u40-b34

Details
Type:
Bug
Submit Date:
2013-08-07
Status:
Closed
Updated Date:
2013-12-13
Project Name:
JDK
Resolved Date:
2013-08-09
Component:
xml
OS:
Sub-Component:
jaxp
CPU:
Priority:
P2
Resolution:
Fixed
Affected Versions:
7u40
Fixed Versions:

Related Reports
Backport:
Backport:
Backport:
Backport:
Relates:

Sub Tasks

Description
Getting errors in  SEPCJVM2008  with the   7 u40 b34 /  b35 .

In  7 u40  b35 
java version "1.7.0_40-ea"
Java(TM) SE Runtime Environment (build 1.7.0_40-ea-b35)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b54, mixed mode)

We see the following issues  in SPECJVM2008   ( e.g.  on Linux but it is likely a cross platform issue ).

   ???.
  Benchmark:   xml.transform
  Run mode:    timed run
  Test type:   multi
  Threads:     8
  Warmup:      60s
  Iterations:  1
  Run length:  60s

xom canonicalization of chess-fo/Kasparov-Karpov.xml.SAX crashed.

 
(Please send xml_out/chess-fo.Kasparov-Karpov.xml.SAX.out or xml_out/chess-fo.Kasparov-Karpov.xml.SAX.out.diff along with the reporter's result.)

Result of chess-fo/Kasparov-Karpov.xml.SAX transformation differs from canonical one.

(Please send xml_out/chess-fo.Kasparov-Karpov.xml.SAX.out or xml_out/chess-fo.Kasparov-Karpov.xml.SAX.out.diff along with the reporter's result.)

xom canonicalization of chess-fo/Kasparov-Karpov.xml.DOM crashed.

(Please send xml_out/chess-fo.Kasparov-Karpov.xml.DOM.out or xml_out/chess-fo.Kasparov-Karpov.xml.DOM.out.diff along with the reporter's result.)

Result of chess-fo/Kasparov-Karpov.xml.DOM transformation differs from canonical one.

(Please send xml_out/chess-fo.Kasparov-Karpov.xml.DOM.out or xml_out/chess-fo.Kasparov-Karpov.xml.DOM.out.diff along with the reporter's result.)

xom canonicalization of chess-fo/Kasparov-Karpov.xml.Stream crashed.

(Please send xml_out/chess-fo.Kasparov-Karpov.xml.Stream.out or xml_out/chess-fo.Kasparov-Karpov.xml.Stream.out.diff along with the reporter's result.)

Result of chess-fo/Kasparov-Karpov.xml.Stream transformation differs from canonical one.

(Please send xml_out/chess-fo.Kasparov-Karpov.xml.Stream.out or xml_out/chess-fo.Kasparov-Karpov.xml.Stream.out.diff along with the reporter's result.)

xom canonicalization of jenitennison/index.xml.SAX crashed.

(Please send xml_out/jenitennison.index.xml.SAX.out or xml_out/jenitennison.index.xml.SAX.out.diff along with the reporter's result.)

Result of jenitennison/index.xml.SAX transformation differs from canonical one.

(Please send xml_out/jenitennison.index.xml.SAX.out or xml_out/jenitennison.index.xml.SAX.out.diff along with the reporter's result.)

xom canonicalization of jenitennison/index.xml.DOM crashed.

???
These errors   do not show up with   7  u25 , e.g.

java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)

Also with older builds  of 7 u40 ( before b34)   they were not seen  .
It seems that these errors  came with the  b34 changes   in  jaxp,  most likely  :

changeset: 8016648: FEATURE_SECURE_PROCESSING set to true or false causes SAXParseException to be thrown
                                    

Comments
The error messages in the report are specific to the Benchmark. There's not enough information to tell where/what went wrong in jaxp.

Can you attach the xml.transform program or a test taken from xml.transform?

For the error message: Result of chess-fo/Kasparov-Karpov.xml.* transformation differs from canonical one. 

Can you attach the result and canonical files?

Thanks.
                                     
2013-08-07
"Also with older builds of 7 u40 ( before b34) they were not seen . "

What was the last successful run before b34, b33?
                                     
2013-08-07
bumped to P2 and added regression as this is showing up in b-34 and did not in prior builds or in 7u25
                                     
2013-08-07
To answer the question about versions.  This was seen in 7u40-b34 and 35.  It was not seen on prior builds of 7u40 that they tested.
It was also not seen on 7u25
                                     
2013-08-07
Kirill,

is it a stopper for 7u40?
                                     
2013-08-08
I have a benchmark set up on my box and have reproduced the errors. I'm in the middle of reading the benchmark test to understand how it works. 
                                     
2013-08-08
The problem is caused by XOM (a popular 3rd party parser) using a different configuration than the JDK default parser. So the fix is to initialize the configuration the same way as the JDK default parser. Risk is low, and we believe this fix should go in since it may be a 7u40 migration issue due to the popularity of this parser.
                                     
2013-08-09
Per discussion at 7u40 Triage on 08/09 - we decided to hold b39 for this fix.  If we find problems with this fix - we will pull it in b40.
                                     
2013-08-09
URL:   http://hg.openjdk.java.net/jdk8/tl/jaxp/rev/4e23bc205d9d
User:  joehw
Date:  2013-08-09 19:42:47 +0000

                                     
2013-08-09
URL:   http://hg.openjdk.java.net/jdk8/tl/jdk/rev/8f01ccb0c981
User:  joehw
Date:  2013-08-09 19:55:32 +0000

                                     
2013-08-09
verified with test results in Nightly
                                     
2013-12-13
Just to add to Joe's comments. This is really the XOM parser having a dependency on JDK-internal classes:

$ jdeps --verbose-level=class xom-1.2.10.jar |grep "JDK internal"
      -> com.sun.org.apache.xerces.internal.parsers.DTDConfiguration JDK internal API (rt.jar)
      -> com.sun.org.apache.xerces.internal.parsers.SAXParser JDK internal API (rt.jar)
      -> com.sun.org.apache.xerces.internal.util.SecurityManager JDK internal API (rt.jar)
      -> com.sun.org.apache.xerces.internal.xni.parser.XMLParserConfiguration JDK internal API (rt.jar)

so it's not really a JDK bug.

Someone should contact the XOM project to make them aware that this dependency might cause them to break at any time. Also I given that these classes are in packages on the restricted package list then I assume this means that XOM doesn't work with a security manager.

                                     
2013-08-12
URL:   http://hg.openjdk.java.net/jdk8/jdk8/jaxp/rev/4e23bc205d9d
User:  lana
Date:  2013-08-26 18:10:24 +0000

                                     
2013-08-26
URL:   http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/8f01ccb0c981
User:  lana
Date:  2013-08-26 18:32:19 +0000

                                     
2013-08-26



Hardware and Software, Engineered to Work Together