Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Message-ID: <23421436.142701283446254293.JavaMail.jira@thor>
Date: Thu, 2 Sep 2010 12:50:54 -0400 (EDT)
From: "Eric Evans (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Subject: [jira] Commented: (AVRO-650) failures under client concurrency
In-Reply-To: <1495096.122151283371618566.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AVRO-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905583#action_12905583 ] 

Eric Evans commented on AVRO-650:
---------------------------------

I apologize for being so terse, I submitted this issue yesterday during a sprint (a Cassandra sprint to work on the Avro RPC interface :)); I didn't have much time, but I didn't want this to go unreported.

I can confirm, in Cassandra this started for us at r987199 when we upgraded Avro to a snapshot based on r986959.  Prior to that we were using jars based on the 1.3.3 release, and this problem did not exist.

> 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.
>         Attachments: 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.