[
https://issues.apache.org/jira/browse/CASSANDRA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803819#action_12803819
]
Jonathan Ellis commented on CASSANDRA-657:
------------------------------------------
moved to trace in r902220
> AntiEntropyService causes lots of errors to be logged during unit tests
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-657
> URL: https://issues.apache.org/jira/browse/CASSANDRA-657
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Stu Hood
> Fix For: 0.6
>
> Attachments: 657-short-lived-connections-for-streaming.patch
>
>
> Some examples from a successful test run on trunk:
> java.io.IOException: Reached an EOL or something bizzare occured. Reading
> from: /127.0.0.1 BufferSizeRemaining: 16
> at org.apache.cassandra.net.io.StartState.doRead(StartState.java:44)
> at org.apache.cassandra.net.io.ProtocolState.read(ProtocolState.java:39)
> at org.apache.cassandra.net.io.TcpReader.read(TcpReader.java:96)
> at
> org.apache.cassandra.net.TcpConnection$ReadWorkItem.run(TcpConnection.java:444)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> ERROR [TCP Selector Manager] 2009-12-29 16:27:53,244 TcpConnection.java (line
> 363) Encountered IOException on connection:
> java.nio.channels.SocketChannel[closed]
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:574)
> at
> org.apache.cassandra.net.TcpConnection.connect(TcpConnection.java:341)
> at
> org.apache.cassandra.net.SelectorManager.doProcess(SelectorManager.java:143)
> at
> org.apache.cassandra.net.SelectorManager.run(SelectorManager.java:107)
> It's not obvious to me if these are errors in AES, errors in the streaming
> code, errors caused because the test environment insufficiently resembles a
> live one, or errors because the test is asking the streaming code to do
> something that doesn't make sense, but AES is definitely at least immediately
> responsible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
