beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-358) JAXB Coder is not thread safe
Date Sat, 25 Jun 2016 16:49:37 GMT

     [ https://issues.apache.org/jira/browse/BEAM-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Halperin updated BEAM-358:
---------------------------------
    Fix Version/s: 0.2.0-incubating

> JAXB Coder is not thread safe
> -----------------------------
>
>                 Key: BEAM-358
>                 URL: https://issues.apache.org/jira/browse/BEAM-358
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Thomas Groh
>             Fix For: 0.2.0-incubating
>
>
> Marshaller and Unmarshaller are cached for reuse in an instance variable. These objects
are not thread safe (http://stackoverflow.com/questions/7400422/jaxb-creating-context-and-marshallers-cost),
so they should be accessed in a single-threaded manner, either via use of a ThreadLocal or
creating a new instance in calls to encode/decode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message