| Summary: | JackrabbitXmlNodeTypeRegistrationTest is failing on Soalris 9 boxes | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Documentation, EDS | Assignee: | David Le Sage <dlesage> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0.ER4 | CC: | jpechane, vhalbert |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2595 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-15 08:56:20 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: | |
|
Description
Jiri Pechanec
2010-11-18 13:31:16 UTC
Try the recommendation in the comment. I do not see any recommendation in Jira comment. Could you please be more specific? Thanks When this problem occurs, it generally indicates there's a problem parsing the xml and that there is a broken XML parser is present in your Java environment. I'd try putting a known good version of xerces in Java's lib/endorsed directory before starting the app, to see if it makes a difference. Jackrabbit currently uses the default XML parser provided by the SAXParserFactory, so broken parsers found "early" in the classloading chain can cause trouble. Please retry with updated xerces jar. Please work with the docs group to get this in to the documentation. The problem is in file owfe_nodetypes.xml. It starts with three special bytes 0000000: efbb bf - UTF-8 BOM When removed the test passes correctly so it is really related to XML parser Writer: Added: Darrin If this is to be documented as a known issue then we need to know: Consequence: how does a user encounter this? how will they recognize that they have this issue ? Cause: why does does it happen ? Fix (Workaround): what do we recommend they do to avoid/fix the problem ? Why does this happen? any time an xml contains an invalid character and cannot be parsed, you could end up with this problem. This could be encountered everywhere an xml file is loaded. And due to the common practice of editing xml files, this could happen in a lot of different places. What's the fix? user has to remove/replace the invalid char(s). A suggested way to verify that an xml file is valid is to open it in a browser. If its invalid, the browser will tell you where the problem is. Assigning to the documentation, if they wish to try to document how to handle this problem. Since this is could be a common problem with any .xml file on the server, any recommendation should probably be put in a global doc. location. Writer: Removed: Darrin Added: dlesage Release Notes Docs Status: Added: Not Yet Documented Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2595 Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2595 Added: https://issues.jboss.org/browse/SOA-2595 The JackrabbitXmlNodeTypeRegistrationTest fails on the Solaris 9 platform. This is caused by the presence of an invalid character in an XML file which results in the system being unable to parse it. This could be encountered whenever any XML file is loaded. To fix this issue, you must edit the file in question to remove any invalid characters. An easy way to verify that XML files are valid is to open them in your web browser. If there is a problem, the browser will identify it for you. Release note created. Verified. |