[
https://issues.apache.org/jira/browse/XALANJ-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971557#comment-13971557
]
Bas Zèro commented on XALANJ-2371:
----------------------------------
Initially it was discussed that a workaround would be to synchronize access to
the Templates.
But that certainly lowers concurrent throughput.
Can anyone comment on how this has been fixed and how it could affect
concurrent throughput? Thanks.
> Possible Templates/Transformers threading issue
> -----------------------------------------------
>
> Key: XALANJ-2371
> URL: https://issues.apache.org/jira/browse/XALANJ-2371
> Project: XalanJ2
> Issue Type: Bug
> Components: transformation
> Affects Versions: 2.7
> Reporter: Tom Fennelly
> Fix For: 2.7.1
>
> Attachments: AVT.diff, XalanConcurrencyBug.zip, xalan-test-v2.zip
>
>
> While running some tests I noticed something strange - applying
> transformations concurrently + unsynchronized using the same template
> instance *appears* to be yielding unexpected results i.e. if I
> synchronize transformations across the threads (synchronize on the
> template instance) I have no issues.
> First reported on the xalan users maillist - more details there:
> http://marc.theaimsgroup.com/?t=117251838500004&r=1&w=2
> I packaged up the test in a maven2 project:
> http://milyn.codehaus.org/xalan/xalan-test-v2.zip
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
