[
https://issues.apache.org/jira/browse/DAFFODIL-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793664#comment-16793664
]
Steve Lawrence commented on DAFFODIL-2097:
------------------------------------------
I was thinking we could just clone the calendar before it's used. That way each
thread gets their own copy. Not sure how that will affect performance, but I
imainge it wouldn't be signifigantly different from storing in the pstate since
that would still require creating new objects.
Long term, we sould just switch to a date time implementation that is thread
safe. ICU has caused nothing but headaches when it comes to datetime stuff.
> Non-thread safe code related to EvCalendar
> ------------------------------------------
>
> Key: DAFFODIL-2097
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2097
> Project: Daffodil
> Issue Type: Task
> Components: Back End
> Reporter: Steve Lawrence
> Assignee: Steve Lawrence
> Priority: Major
> Fix For: 2.4.0
>
>
> When we use the EvCalendar, this results in a calendar that is often shared
> among threads. Since this calendar is modify by the SimpleDateTime parse and
> format functins, different threads using the same calendar could interact and
> cause spurious failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
