[
https://issues.apache.org/jira/browse/WINK-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021170#comment-13021170
]
Hudson commented on WINK-345:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #457 (See
[https://hudson.apache.org/hudson/job/Wink-Trunk-JDK1.5/457/])
Once marshaller is released, don't re-use
Fixes [WINK-345].
Thanks to Matt for reporting the issue.
> AbstractJAXBCollectionProvider write method is placing Marshaller back in
> pool before it is done being used.
> ------------------------------------------------------------------------------------------------------------
>
> Key: WINK-345
> URL: https://issues.apache.org/jira/browse/WINK-345
> Project: Wink
> Issue Type: Bug
> Components: Common
> Affects Versions: 1.1.2
> Reporter: Matt
> Priority: Critical
>
> Within the write() method in the AbstractJAXBCollectionProvider class, a for
> each loop is used to marshall each object in the elementArray. Within this
> for loop, right before the next iteration is made, the marshaller that is
> being used is released back to the marshaller pool. The remaining elements
> will then be iterated upon using the same marshaller because the marshaller
> pointer that is referred to is not null. This creates the possibility of a
> single marshaller being used by multiple threads.
> In version 1.1.2, see line 167 for the referred to null check and line 187
> for the misplaced releaseJAXBMarshaller() method call.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
