[FLUME-2386] Exceptions handing in SyslogTcpSource

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.4.0
• Assignee: Unassigned
• Reporter: Michalis Kongtongk
• Created: 15/May/14 13:01
• Updated: 15/May/14 13:01

Description

Application is not properly closing the connection eg: we see RST in tcpdump eg: tcpdump filter: 'tcp[13] & 4!=0'

Flume exceptions are generated in /var/log/flume-ng/flume.init.log instead of catching them and handling them.

Example:

Apr 10, 2014 11:41:00 AM org.jboss.netty.channel.SimpleChannelHandler 
WARNING: EXCEPTION, please implement org.apache.flume.source.SyslogTcpSource$syslogTcpHandler.exceptionCaught() for proper handling. 
java.io.IOException: Connection reset by peer 
at sun.nio.ch.FileDispatcher.read0(Native Method) 
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21) 
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198) 
at sun.nio.ch.IOUtil.read(IOUtil.java:166) 
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:245) 
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:63) 
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:373)
at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:247) 
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35) 
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 
at java.lang.Thread.run(Thread.java:662)