Bug #5130
closed`saxon:discard-document()` should be synchronized
100%
Description
The extension function saxon:discard-document()
makes multiple updates to data held by the Controller, in particular the document pool and the list of unavailable documents. The method should be synchronized in case there are multiple simultaneous calls to saxon:discard-document()
in different threads.
Ideally we should also provide a function that combines the effect of doc() and discard-document() -- and perhaps doc-available() -- all within a single call having atomic effect, but meanwhile simply synchronising discard-document() will remove some potential dangers.
(This is relevant only when transformations are executing in multiple threads, typically as a result of using xsl:result-document).
Related issues
Updated by Michael Kay about 3 years ago
- Status changed from New to Resolved
- Applies to branch 10, 11, trunk added
- Fix Committed on Branch 10, trunk added
Fixed on the 10 and 11 branches.
Updated by Michael Kay about 3 years ago
- Related to Support #5124: Unexpected error "Cannot read a document that was written during the same transformation" - race condition added
Updated by O'Neil Delpratt almost 3 years ago
- % Done changed from 0 to 100
- Fixed in Maintenance Release 11.1 added
- Platforms .NET, Java added
Bug fix applied in the Saxon 11.1 release.
Updated by O'Neil Delpratt almost 3 years ago
Leaving bug as resolved until fix applied to the Saxon 10 maintenance release.
Updated by Debbie Lockett over 2 years ago
- Status changed from Resolved to Closed
- Fixed in Maintenance Release 10.7 added
- Fixed in Maintenance Release deleted (
11.1)
Bug fix applied in the Saxon 10.7 maintenance release.
Updated by Debbie Lockett over 2 years ago
- Fixed in Maintenance Release 11.1 added
Please register to edit this issue