You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2020/03/03 15:37:00 UTC
[jira] [Resolved] (DAFFODIL-2284) Non-thread safe failures with
JSON schema
[ https://issues.apache.org/jira/browse/DAFFODIL-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lawrence resolved DAFFODIL-2284.
--------------------------------------
Resolution: Fixed
Fixed in commit f2e0fd92fb7f8a44fa4c2c27e458a89e10e8d0d1
> Non-thread safe failures with JSON schema
> -----------------------------------------
>
> Key: DAFFODIL-2284
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2284
> Project: Daffodil
> Issue Type: Bug
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Priority: Blocker
> Fix For: 2.6.0
>
> Attachments: json5.dfdl.xsd, random.json
>
>
> Commit 7e8e1b3ed110efe939908cdf1e12df50d1f86527 causes random failures when doing performance tests with a JSON schema (schema and test file attached), e.g.:
> {code}
> daffodil performance -s json.dfdl.xsd -t 2 -N 2 random.json
> {code}
> The likely cause is that we've always had some non-thread-safe code that we just never happened to hit. But with that commit, there is much more sharing going on and so much more likely for non-thread-safe code to get triggered. No other information as to where the bad code is, but it's very repeatable with this schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)