[
https://issues.apache.org/jira/browse/AVRO-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-650:
------------------------------
Attachment: AVRO-650.patch
Scott, thanks for the analysis!
I'd prefer to fix this by making DatumReader#read(T,Decoder) thread-safe, in
part because a Responder is user-created and hence hard to construct without
adding a factory API, but moreover I think it's a nicer API. Clearly Encoder &
Decoder have state, but a DatumReader & DatumWriter shouldn't once constructed
and configured.
Here's a patch that I think achieves this, by adding a ThreadLocal for the
resolver.
Eric, can you please try this? Thanks!
> failures under client concurrency
> ---------------------------------
>
> Key: AVRO-650
> URL: https://issues.apache.org/jira/browse/AVRO-650
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.4.0
> Reporter: Eric Evans
> Assignee: Thiruvalluvan M. G.
> Priority: Blocker
> Attachments: AVRO-650.patch, exceptions.txt, tester.py
>
>
> I'm having trouble getting any client concurrency out of cassandra's rpc
> server. Running the attached `tester.py' from more than one terminal window
> is enough to generate the exceptions seen in `exceptions.txt'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
