[
https://issues.apache.org/jira/browse/CASSANDRA-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125838#comment-16125838
]
Aleksey Yeschenko commented on CASSANDRA-13363:
-----------------------------------------------
The problem is real, and the patch does work, but I'm afraid it doesn't quite
solve the issue completely.
There is also an issue involving {{serializedSize()}}. {{index}} field might be
empty at the time when we calculate the size of the message, and switch to
non-empty afterwards. It's not currently an issue since {{READ_COMMAND}} is not
using a {{CallbackDeterminedSerializer}} but it's still a bug.
The proper fix would be to make sure the field never changes and is only set
once at construction time. While at it, might also want to refactor it to not
be {{Optional}}. {{Optional}} is reserved for return types, not object fields
and method arguments.
Give me a couple hours to try work it out properly?
> java.lang.ArrayIndexOutOfBoundsException: null
> ----------------------------------------------
>
> Key: CASSANDRA-13363
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13363
> Project: Cassandra
> Issue Type: Bug
> Environment: CentOS 6, Cassandra 3.10
> Reporter: Artem Rokhin
> Assignee: zhaoyan
> Priority: Critical
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> Constantly see this error in the log without any additional information or a
> stack trace.
> {code}
> Exception in thread Thread[MessagingService-Incoming-/10.0.1.26,5,main]
> {code}
> {code}
> java.lang.ArrayIndexOutOfBoundsException: null
> {code}
> Logger: org.apache.cassandra.service.CassandraDaemon
> Thrdead: MessagingService-Incoming-/10.0.1.12
> Method: uncaughtException
> File: CassandraDaemon.java
> Line: 229
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
