[
https://issues.apache.org/jira/browse/DIRECTMEMORY-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703136#comment-13703136
]
Hudson commented on DIRECTMEMORY-129:
-------------------------------------
Integrated in directmemory-trunk #383 (See
[https://builds.apache.org/job/directmemory-trunk/383/])
DIRECTMEMORY-129 - applied Chetan's patch for using a pool of
KryoSerializers (Revision 1501181)
Result = SUCCESS
tommaso :
Files :
*
/directmemory/trunk/directmemory-cache/src/main/java/org/apache/directmemory/cache/CacheServiceImpl.java
*
/directmemory/trunk/serializers/kryo/src/main/java/org/apache/directmemory/serialization/kryo/KryoSerializer.java
> 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
> Assignee: Tommaso Teofili
> Priority: Minor
> Fix For: 0.2
>
> 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
