Bug 1119927
Summary: | When using JVM 1.7.0_40 or later, server logs SAXParserImpl parsing errors indicating property is not recognized. | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | Larry O'Leary <loleary> |
Component: | Core Server | Assignee: | Jay Shaughnessy <jshaughn> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | JON 3.1.2 | CC: | jshaughn |
Target Milestone: | DR01 | ||
Target Release: | JON 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The Xerces library included in the JON enterprise container did not support the accessExternalDTD or entityExpansionLimit properties, which caused ERROR messages to appear on server start and in server.log. The Xerces library has been removed from the product and replaced with a version where the bug was patched upstream, fixing the originally-reported issue.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-12-11 14:02:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Larry O'Leary
2014-07-15 21:13:45 UTC
It seems the warnings are due to the 3rd party Xerces lib we use for parsing, which is unaware of the newer properties attempting to be set on the parser. We can see in this Java code snippet that the accessExternalDTD property should not be an issue. The parser code protects things and the unrecognized property generates only a log message: See Lines 480:487, http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/7u40-b43/com/sun/org/apache/xalan/internal/xsltc/compiler/Parser.java?av=f Looking to see about the other property... I can't definitively locate the call generating the SAXNotRecognizedException for ENTITY_EXPANSION_LIMIT. But it's most likely generated when the limit is trying to be set. It is likely tryng to be set to the default of 64000, but since this version of xerces does not know about the property it throws the exception, which is very likely just logged by the caller. Overall, I'd suggest these messages be ignored unless this second message can be linked to some errant behavior (the other is safe, as described above), which is unlikely. The workaround, I believe, would be to back up to Java7 u25. This should not be an issue in 3.3.0 because we no longer use the problematic xerces lib. Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993 |