[ 
https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273378#comment-16273378
 ] 

Michael Glavassevich edited comment on XERCESJ-1687 at 11/30/17 8:40 PM:
-------------------------------------------------------------------------

Until there's a fix to the Eclipse library that Xerces can consume, I think the 
only way to get around this on our side would be synchronize all access to 
PsychoPath using a 'static' object for synchronization. I can imagine that 
would be very bad for performance. Only one thread at a time could make 
progress but at least it would work functionally.

I recall Apache BCEL has (or had) similar thread-safety issues and that was the 
approach some users took to work around it.


was (Author: [email protected]):
Until there's a fix to the Eclipse library that Xerces can consume, I think the 
only way to get around this on our side would be synchronize all access to 
PsychoPath using a 'static' object for synchronization. I can imagine that 
would be very bad for performance. Only one thread a time could make progress 
but at least it would work functionally.

> 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: XML Schema 1.1 Structures
>    Affects Versions: 2.12.0
>         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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to