Hello,

Thanks for the help. There was a problem in the code actually... The connection object was not thread safe. That is why the messages were so big. 

After fixing that we do not get any errors. The cluster seems stable.

Thanks again for all the help.

Regards,

Vasilis



On Thu, Jul 5, 2012 at 11:32 PM, aaron morton <aaron@thelastpickle.com> wrote:
agree. 

It's a good idea to remove as many variables and possible and get to a stable/known state. Use a clean install and a well known client and see if the problems persist. 

Cheers
 
-----------------
Aaron Morton
Freelance Developer
@aaronmorton

On 5/07/2012, at 4:58 PM, Tristan Seligmann wrote:

On Jul 4, 2012 2:02 PM, "Vasileios Vlachos" <vasileiosvlachos@gmail.com> wrote:
>
> Any ideas what could be causing strange message lengths?

One cause of this that I've seen is a client using unframed Thrift transport while the server expects framed, or vice versa. I suppose a similar cause could be something that is not a Thrift client at all mistakenly connecting to Cassandra's Thrift port.