You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by aaron morton <aa...@thelastpickle.com> on 2013/04/18 10:05:00 UTC
Re:
> ERROR 08:40:42,684 Error occurred during processing of message.
> java.lang.StringIndexOutOfBoundsException: String index out of range: -214741811
> 1
> at java.lang.String.checkBounds(String.java:397)
> at java.lang.String.<init>(String.java:442)
> at org.apache.thrift.protocol.TBinaryProtocol.readString(TBinaryProtocol
> .java:339)
> at org.apache.cassandra.thrift.Cassandra$batch_mutate_args.read(Cassandr
This is an error when the server is trying to read what the client has sent.
> Is this caused due to my application putting any corrupted data?
Looks that way. What client are you using ?
Cheers
-----------------
Aaron Morton
Freelance Cassandra Consultant
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 18/04/2013, at 3:21 PM, Ertio Lew <er...@gmail.com> wrote:
> I run cassandra on single win 8 machine for development needs. Everything has been working fine for several months but just today I saw this error message in cassandra logs & all host pools were marked down.
>
>
> ERROR 08:40:42,684 Error occurred during processing of message.
> java.lang.StringIndexOutOfBoundsException: String index out of range: -214741811
> 1
> at java.lang.String.checkBounds(String.java:397)
> at java.lang.String.<init>(String.java:442)
> at org.apache.thrift.protocol.TBinaryProtocol.readString(TBinaryProtocol
> .java:339)
> at org.apache.cassandra.thrift.Cassandra$batch_mutate_args.read(Cassandr
> a.java:18958)
> at org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.process(
> Cassandra.java:3441)
> at org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.jav
> a:2889)
> at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run
> (CustomTThreadPoolServer.java:187)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:908)
> at java.lang.Thread.run(Thread.java:662)
>
>
> After restarting the server everything again worked fine.
> I am curious to know what is this related to. Is this caused due to my application putting any corrupted data?
>
>
Re:
Posted by Ertio Lew <er...@gmail.com>.
I use hector
On Thu, Apr 18, 2013 at 1:35 PM, aaron morton <aa...@thelastpickle.com>wrote:
> > ERROR 08:40:42,684 Error occurred during processing of message.
> > java.lang.StringIndexOutOfBoundsException: String index out of range:
> -214741811
> > 1
> > at java.lang.String.checkBounds(String.java:397)
> > at java.lang.String.<init>(String.java:442)
> > at
> org.apache.thrift.protocol.TBinaryProtocol.readString(TBinaryProtocol
> > .java:339)
> > at
> org.apache.cassandra.thrift.Cassandra$batch_mutate_args.read(Cassandr
> This is an error when the server is trying to read what the client has
> sent.
>
> > Is this caused due to my application putting any corrupted data?
> Looks that way. What client are you using ?
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.thelastpickle.com
>
> On 18/04/2013, at 3:21 PM, Ertio Lew <er...@gmail.com> wrote:
>
> > I run cassandra on single win 8 machine for development needs.
> Everything has been working fine for several months but just today I saw
> this error message in cassandra logs & all host pools were marked down.
> >
> >
> > ERROR 08:40:42,684 Error occurred during processing of message.
> > java.lang.StringIndexOutOfBoundsException: String index out of range:
> -214741811
> > 1
> > at java.lang.String.checkBounds(String.java:397)
> > at java.lang.String.<init>(String.java:442)
> > at
> org.apache.thrift.protocol.TBinaryProtocol.readString(TBinaryProtocol
> > .java:339)
> > at
> org.apache.cassandra.thrift.Cassandra$batch_mutate_args.read(Cassandr
> > a.java:18958)
> > at
> org.apache.cassandra.thrift.Cassandra$Processor$batch_mutate.process(
> > Cassandra.java:3441)
> > at
> org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.jav
> > a:2889)
> > at
> org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run
> > (CustomTThreadPoolServer.java:187)
> > at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> > utor.java:886)
> > at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> > .java:908)
> > at java.lang.Thread.run(Thread.java:662)
> >
> >
> > After restarting the server everything again worked fine.
> > I am curious to know what is this related to. Is this caused due to my
> application putting any corrupted data?
> >
> >
>
>