-
Bug
-
Resolution: Fixed
-
P2
-
7u40
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8023035 | 7u60 | Joe Wang | P2 | Resolved | Fixed | b01 |
JDK-8022846 | 7u51 | Joe Wang | P2 | Resolved | Fixed | b01 |
JDK-8022841 | 7u45 | Joe Wang | P2 | Resolved | Fixed | b07 |
JDK-8022739 | 7u40 | Joe Wang | P2 | Closed | Fixed | b39 |
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
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
- backported by
-
JDK-8022841 SPECJVM2008 has errors introduced in 7u40-b34
-
- Resolved
-
-
JDK-8022846 SPECJVM2008 has errors introduced in 7u40-b34
-
- Resolved
-
-
JDK-8023035 SPECJVM2008 has errors introduced in 7u40-b34
-
- Resolved
-
-
JDK-8022739 SPECJVM2008 has errors introduced in 7u40-b34
-
- Closed
-
- relates to
-
JDK-8024876 [TEST_BUG] javax/xml/jaxp/parsers/8022548/XOMParserTest.java failed when testbase dir has read only permissions
-
- Resolved
-