directmemory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRECTMEMORY-129) Kryo serializer usage is not thread safe
Date Tue, 09 Jul 2013 10:11:51 GMT

    [ https://issues.apache.org/jira/browse/DIRECTMEMORY-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703114#comment-13703114
] 

Tommaso Teofili commented on DIRECTMEMORY-129:
----------------------------------------------

patch looks good Chetan, I've applied it at r1501181, thanks! :)
                
> Kryo serializer usage is not thread safe
> ----------------------------------------
>
>                 Key: DIRECTMEMORY-129
>                 URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-129
>             Project: Apache DirectMemory
>          Issue Type: Bug
>          Components: Serializers
>    Affects Versions: 0.1-incubating
>            Reporter: Chetan Mehrotra
>            Priority: Minor
>         Attachments: DIRECTMEMORY-129-1.patch
>
>
> KryoSerializer uses a instance level Kryo object which is accessed concurrently. As per
Kryo 2.x docs [1] the Kryo object is not threadsafe. As a fix one should use a pool of Kryo
instances
> [1] https://code.google.com/p/kryo/#Threading

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message