cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Hermes (JIRA)" <>
Subject [jira] Created: (CASSANDRA-1290) Cassandra-cli doesn't use framed transport by default
Date Fri, 16 Jul 2010 20:55:50 GMT
Cassandra-cli doesn't use framed transport by default

                 Key: CASSANDRA-1290
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 0.7
            Reporter: Jon Hermes
            Assignee: Jon Hermes
            Priority: Minor
             Fix For: 0.7

Spawned by CASSANDRA-475 .
The cli uses non-framed transport, which causes errors on connection that look like:

cli:{noformat}$ bin/cassandra-cli 
Welcome to cassandra CLI.

Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
[default@unknown] connect
Exception retrieving information about the cassandra node, check you have connected to the
thrift port.{noformat}

cass:{noformat}ERROR 15:48:12,523 Thrift error occurred during processing of message.
org.apache.thrift.TException: Message length exceeded: 1684370275
	at org.apache.thrift.protocol.TBinaryProtocol.checkReadLength(
	at org.apache.thrift.protocol.TBinaryProtocol.readStringBody(
	at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(
	at org.apache.cassandra.thrift.Cassandra$Processor.process(
	at org.apache.cassandra.thrift.CustomTThreadPoolServer$
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

Changing it to use framed transport fixes this, and it should be using framed transport by
default regardless.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message