[
https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330640#comment-16330640
]
Mukul Gandhi commented on XERCESJ-1687:
---------------------------------------
I tried the following thing.
XML => used what you've provided in your test case.
XSD,
I used XSD from your test case, but had only following random asserts,
<xsd:assert test="count(.//*) gt 0"/>
<xsd:assert test=".//stuff"/>
(and used everything else from your XSD)
This results in no failure of test cases.
IMHO, your claim that most of Xerces's XPath2 processor is affected by the
multi-threaded bug that you've posted, is not true. It seems, certain XPath
expressions cause the problem you've mentioned – I think, we'd be ok to mention
facts related to this in our release notes (or documentation).
Please consider giving a less severe priority to your bug report.
> XSD 1.1 validation with xs:assert is not thread safe
> ----------------------------------------------------
>
> Key: XERCESJ-1687
> URL: https://issues.apache.org/jira/browse/XERCESJ-1687
> Project: Xerces2-J
> Issue Type: Bug
> Components: JAXP (javax.xml.validation)
> Environment: java 8 / java 9
> Reporter: Stephan Trebels
> Priority: Critical
> Attachments: parallel-test.zip
>
>
> The XSD 1.1 validation code uses eclipse webtools xpath to validate
> assertions. The PsychoPath XPath 2.0 engine has a bug in
> ResultSequenceFactory, which invalidates correct execution in all parallel
> invocation of XSD 1.1 validation.
> This issue affects completely unrelated schemas and input XML, as long as
> both use assertions. The effect is a lot of spurious assert violations. The
> issue is visible even if only two threads are used in parallel.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=527812
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
