[
https://issues.apache.org/jira/browse/FLUME-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243915#comment-13243915
]
Hudson commented on FLUME-1074:
-------------------------------
Integrated in flume-trunk #154 (See
[https://builds.apache.org/job/flume-trunk/154/])
FLUME-1074. Fix exception handling in AvroSink.
(Prasad Mujumdar via Arvind Prabhakar) (Revision 1308197)
Result = SUCCESS
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1308197
Files :
*
/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/channel/ChannelProcessor.java
*
/incubator/flume/trunk/flume-ng-core/src/main/java/org/apache/flume/sink/AvroSink.java
> 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
> Assignee: Prasad Mujumdar
> Fix For: v1.2.0
>
> Attachments: FLUME-1074.patch
>
>
> 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
