[
https://issues.apache.org/jira/browse/CASSANDRA-19218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated CASSANDRA-19218:
---------------------------------------
Description:
This is not a critical issue, but the errors thrown when we try to connect with
incompatible messaging version (for example from an sstable loader) are odd. We
get weird looking class cast exceptions like this:
{noformat}
Session peer /127.0.0.1:7012 Failed because of an unknown exception
java.lang.ClassCastException: class
org.apache.cassandra.net.OutboundConnectionInitiator$Result$Incompatible cannot
be cast to class
org.apache.cassandra.net.OutboundConnectionInitiator$Result$Success
(org.apache.cassandra.net.OutboundConnectionInitiator$Result$Incompatible and
org.apache.cassandra.net.OutboundConnectionInitiator$Result$Success are in
unnamed module of loader 'app')
org.apache.cassandra.net.OutboundConnectionInitiator$Result.success(OutboundConnectionInitiator.java:520)
org.apache.cassandra.streaming.async.NettyStreamingConnectionFactory.connect(NettyStreamingConnectionFactory.java:68){noformat}
We should probably handle that somehow and error out with a reasonable message,
which at least would prove that we consciously refuse to connect.
was:
This is not a critical issue, but the errors thrown when we try to connect with
incompatible messaging version (for example from an sstable loader) are odd. We
get weird looking class cast exceptions like this:
{format}
Session peer /127.0.0.1:7012 Failed because of an unknown exception
java.lang.ClassCastException: class
org.apache.cassandra.net.OutboundConnectionInitiator$Result$Incompatible cannot
be cast to class
org.apache.cassandra.net.OutboundConnectionInitiator$Result$Success
(org.apache.cassandra.net.OutboundConnectionInitiator$Result$Incompatible and
org.apache.cassandra.net.OutboundConnectionInitiator$Result$Success are in
unnamed module of loader 'app')
org.apache.cassandra.net.OutboundConnectionInitiator$Result.success(OutboundConnectionInitiator.java:520)
org.apache.cassandra.streaming.async.NettyStreamingConnectionFactory.connect(NettyStreamingConnectionFactory.java:68)
{format}
We should probably handle that somehow and error out with a reasonable message,
which at least would prove that we consciously refuse to connect.
> NettyStreamingConnectionFactory lacks handling of outcomes other than success
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-19218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19218
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Streaming and Messaging
> Reporter: Jacek Lewandowski
> Priority: Low
> Fix For: 4.1.x, 5.0.x, 5.x
>
>
> This is not a critical issue, but the errors thrown when we try to connect
> with incompatible messaging version (for example from an sstable loader) are
> odd. We get weird looking class cast exceptions like this:
> {noformat}
> Session peer /127.0.0.1:7012 Failed because of an unknown exception
> java.lang.ClassCastException: class
> org.apache.cassandra.net.OutboundConnectionInitiator$Result$Incompatible
> cannot be cast to class
> org.apache.cassandra.net.OutboundConnectionInitiator$Result$Success
> (org.apache.cassandra.net.OutboundConnectionInitiator$Result$Incompatible and
> org.apache.cassandra.net.OutboundConnectionInitiator$Result$Success are in
> unnamed module of loader 'app')
>
> org.apache.cassandra.net.OutboundConnectionInitiator$Result.success(OutboundConnectionInitiator.java:520)
>
> org.apache.cassandra.streaming.async.NettyStreamingConnectionFactory.connect(NettyStreamingConnectionFactory.java:68){noformat}
> We should probably handle that somehow and error out with a reasonable
> message, which at least would prove that we consciously refuse to connect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
