You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Jay Liu (JIRA)" <ji...@apache.org> on 2013/06/14 06:52:20 UTC

[jira] [Commented] (FLUME-2052) Flume hangs on malformed characters while proccesing

    [ https://issues.apache.org/jira/browse/FLUME-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683092#comment-13683092 ] 

Jay Liu commented on FLUME-2052:
--------------------------------

This is a major show stopper for us. I agree that it should skip such characters.
                
> Flume hangs on malformed characters while proccesing
> ----------------------------------------------------
>
>                 Key: FLUME-2052
>                 URL: https://issues.apache.org/jira/browse/FLUME-2052
>             Project: Flume
>          Issue Type: Bug
>         Environment: centOS 6.3
> Flume 1.3.0
>            Reporter: greg glazeweas
>              Labels: MalformedInputException, charset, flume
>
> When parsing a file with messed up encoding flume spits this error:
> 23 May 2013 22:06:29,446 ERROR [pool-12-thread-1] (org.apache.flume.source.SpoolDirectorySource$SpoolDirectoryRunnable.run:164)  - Uncaught exception in Runnable
> java.nio.charset.MalformedInputException: Input length = 1
>         at java.nio.charset.CoderResult.throwException(CoderResult.java:277)
>         at org.apache.flume.serialization.ResettableFileInputStream.readChar(ResettableFileInputStream.java:162)
>         at org.apache.flume.serialization.LineDeserializer.readLine(LineDeserializer.java:134)
>         at org.apache.flume.serialization.LineDeserializer.readEvent(LineDeserializer.java:72)
>         at org.apache.flume.serialization.LineDeserializer.readEvents(LineDeserializer.java:91)
>         at org.apache.flume.client.avro.ReliableSpoolingFileEventReader.readEvents(ReliableSpoolingFileEventReader.java:221)
>         at org.apache.flume.source.SpoolDirectorySource$SpoolDirectoryRunnable.run(SpoolDirectorySource.java:154)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>         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:722)
> It would be good to skip such characters, ignore them or delete. Corrupt signs come from spamming engines, flume cant handle them at all.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira