You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/04 21:59:39 UTC

[jira] [Resolved] (CASSANDRA-2827) Thrift error

     [ https://issues.apache.org/jira/browse/CASSANDRA-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-2827.
---------------------------------------

    Resolution: Invalid

Either you're using a Hector connection in a thread-unsafe way, or there is a Hector bug.
                
> Thrift error
> ------------
>
>                 Key: CASSANDRA-2827
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2827
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.4
>         Environment: 2 nodes with 0.7.4 on linux
>            Reporter: Olivier Smadja
>
> This exeception occured of a non seed node.
> ERROR [pool-1-thread-9] 2011-06-25 17:41:37,723 CustomTThreadPoolServer.java (line 218) Thrift error occurred during processing of message.
> org.apache.thrift.TException: Negative length: -2147418111
> 	at org.apache.thrift.protocol.TBinaryProtocol.checkReadLength(TBinaryProtocol.java:388)
> 	at org.apache.thrift.protocol.TBinaryProtocol.readBinary(TBinaryProtocol.java:363)
> 	at org.apache.cassandra.thrift.Cassandra$batch_mutate_args.read(Cassandra.java:15964)
> 	at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.process(Cassandra.java:3023)
> 	at org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.java:2555)
> 	at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:206)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> 	at java.lang.Thread.run(Thread.java:619)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira