You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Brock Noland (Commented) (JIRA)" <ji...@apache.org> on 2012/03/29 00:45:28 UTC

[jira] [Commented] (FLUME-1074) AvroSink if any non-caught exception is thrown, an exception is thrown in finally clause

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

Brock Noland commented on FLUME-1074:
-------------------------------------

This is also true for HDFSEvent sink if a non-Exception throwable is thrown.
                
> AvroSink if any non-caught exception is thrown, an exception is thrown in finally clause
> ----------------------------------------------------------------------------------------
>
>                 Key: FLUME-1074
>                 URL: https://issues.apache.org/jira/browse/FLUME-1074
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v1.1.0
>            Reporter: Brock Noland
>
> If AvroSink and perhaps others, if any non-caught exception is thrown before transaction.commit, the finally clause throws:
> 2012-03-28 17:31:24,560 ERROR org.apache.flume.SinkRunner: Unhandled exception, logging and sleeping for 5000ms
> java.lang.IllegalStateException: close() called when transaction is OPEN - you must either commit or rollback first
>         at com.google.common.base.Preconditions.checkState(Preconditions.java:172)
>         at org.apache.flume.channel.BasicTransactionSemantics.close(BasicTransactionSemantics.java:179)
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:269)
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:118)
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:148)
>         at java.lang.Thread.run(Thread.java:662)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira