[
https://issues.apache.org/jira/browse/FLUME-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086348#comment-13086348
]
Jonathan Hsieh commented on FLUME-742:
--------------------------------------
The test processing getting killed is actually due to a 480s individual
testclass timeout.
{code}
<artifactId>maven-surefire-plugin</artifactId>
<version>2.8.1</version>
<configuration>
<forkMode>always</forkMode>
<forkedProcessTimeoutInSeconds>480</forkedProcessTimeoutInSeconds>
{code}
I noticed that when TestAvroSinks timesout, the process running it doesn't seem
to get killed, so I believe that TestThriftSinks fails because it tries to bind
to the same ports as the TestAvroSinks used but did not release.
> TestAvroSinks fails
> -------------------
>
> Key: FLUME-742
> URL: https://issues.apache.org/jira/browse/FLUME-742
> Project: Flume
> Issue Type: Bug
> Reporter: Tom White
> Assignee: Tom White
> Attachments: FLUME-742.patch, FLUME-742.patch
>
>
> The following appears in the log
> {noformat}
> 2011-08-12 21:21:48,784 [Thread-13] INFO avro.AvroEventSink: AvroEventSink
> open on port 35854
> 2011-08-12 21:21:48,863 [Thread-13] INFO debug.MemorySinkSource: Closing mem
> source sink that has 25 elements
> 2011-08-12 21:21:48,863 [Thread-13] INFO avro.AvroEventSink: AvroEventSink on
> port 35854 closed
> Exception in thread "Thread-13" java.lang.NullPointerException
> at
> com.cloudera.flume.handlers.avro.AvroEventSink.getSentBytes(AvroEventSink.java:116)
> at
> com.cloudera.flume.handlers.avro.TestAvroSinks$3.run(TestAvroSinks.java:196)
> {noformat}
> Then the test (testManyThreadsAvroSend) times out.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
