This is a bug of the jdk older than jdk1.6.0_18.
Problem resolved after updating the jdk.
Bug of the file channel :
http://bugs.sun.com/view_bug.do?bug_id=5103988
Fixed in version 6u18 :
http://java.sun.com/javase/6/webnotes/6u18.html



------------------  
casablinca126.com
2010-03-19

-------------------------------------------------------------
发件人:Jonathan Ellis
发送日期:2010-03-17 21:27:55
收件人:u...@cassandra.apache.org
抄送:
主题:Re: exception when adding new node

This is harmless.

2010/3/17 casablinca126.com  <casabli...@126.com >:
> 爃ello ,
> ???營 try to add a new node to a 2-node cluster, an exception occured while 
> transferring data to the new node:
>
> WARN - Running on default stage - beware
> WARN - Problem reading from socket connected to : 
> java.nio.channels.SocketChannel[connected local=/192.168.13.39:35182 
> remote=/192.168.13.107:7000]
> WARN - Exception was generated at : 03/17/2010 16:45:12 on thread 
> MESSAGING-SERVICE-POOL:2
> Reached an EOL or something bizzare occured. Reading from: /192.168.13.107 
> BufferSizeRemaining: 16
> java.io.IOException: Reached an EOL or something bizzare occured. Reading 
> from: /192.168.13.107 BufferSizeRemaining: 16
> ???燼t org.apache.cassandra.net.io.StartState.doRead(StartState.java:44)
> ???燼t org.apache.cassandra.net.io.ProtocolState.read(ProtocolState.java:39)
> ???燼t org.apache.cassandra.net.io.TcpReader.read(TcpReader.java:95)
> ???燼t 
> org.apache.cassandra.net.TcpConnection$ReadWorkItem.run(TcpConnection.java:445)
> ???燼t 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> ???燼t 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> ???燼t java.lang.Thread.run(Thread.java:619)
>
> INFO - Closing errored connection java.nio.channels.SocketChannel[connected 
> local=/192.168.13.39:35182 remote=/192.168.13.107:7000]
>
> I'm using cassandra-0.5.0, the ReplicationFactor is 2. The network seems OK, 
> but I still get this exception.
> Any ideas?
>
>
> --------------
> casablinca126.com
> 2010-03-17
>
>
>

Reply via email to