You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Tyler Hobbs (JIRA)" <ji...@apache.org> on 2014/06/24 18:10:31 UTC
[jira] [Updated] (CASSANDRA-7440) Unrecognized opcode or flag
causes ArrayIndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/CASSANDRA-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tyler Hobbs updated CASSANDRA-7440:
-----------------------------------
Description:
If an unrecognized opcode or flag is used in a native protocol message, it results in an unhandled ArrayIndexOutOfBoundsException server-side. This can happen when features from a new protocol version are used with an older version of Cassandra.
Here's one example stacktrace:
{noformat}
ERROR [Native-Transport-Requests:5] 2014-06-24 11:09:50,167 ErrorMessage.java (line 210) Unexpected exception during request
java.lang.ArrayIndexOutOfBoundsException: 15
at org.apache.cassandra.transport.Message$Type.fromOpcode(Message.java:102)
at org.apache.cassandra.transport.Frame$Decoder.decode(Frame.java:179)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
was:
If an unrecognized opcode or flag is used in a native protocol message, it results in an unhandled ArrayIndexOutOfBoundsException server-side. This can happen when features from a new protocol version are used with an older protocol version.
Here's one example stacktrace:
{noformat}
ERROR [Native-Transport-Requests:5] 2014-06-24 11:09:50,167 ErrorMessage.java (line 210) Unexpected exception during request
java.lang.ArrayIndexOutOfBoundsException: 15
at org.apache.cassandra.transport.Message$Type.fromOpcode(Message.java:102)
at org.apache.cassandra.transport.Frame$Decoder.decode(Frame.java:179)
at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
> Unrecognized opcode or flag causes ArrayIndexOutOfBoundsException
> -----------------------------------------------------------------
>
> Key: CASSANDRA-7440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7440
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Tyler Hobbs
> Priority: Minor
> Fix For: 2.0.9, 2.1 rc2
>
>
> If an unrecognized opcode or flag is used in a native protocol message, it results in an unhandled ArrayIndexOutOfBoundsException server-side. This can happen when features from a new protocol version are used with an older version of Cassandra.
> Here's one example stacktrace:
> {noformat}
> ERROR [Native-Transport-Requests:5] 2014-06-24 11:09:50,167 ErrorMessage.java (line 210) Unexpected exception during request
> java.lang.ArrayIndexOutOfBoundsException: 15
> at org.apache.cassandra.transport.Message$Type.fromOpcode(Message.java:102)
> at org.apache.cassandra.transport.Frame$Decoder.decode(Frame.java:179)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109)
> at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
> at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)