You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2013/01/24 02:15:40 UTC

Please test

After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?

Thanks,
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
I didn't try upgrading to 1.3.1.  I can try that and see.

I do know that Flume the embedded appenders won't be compatible with 1.4 when it is released.  Flume actually created embedded support at my request and some of the classes we are currently using have disappeared.  In addition, the Avro "remote" version of the appender could be using Flume's RPCClient, which takes care of failing over from one agent to another for you so it would make the Manager a bit simpler.

The main thing is simply that now that it seems to be working I can go ahead and do the beta4 release.

Ralph


On Jan 27, 2013, at 5:53 PM, Gary Gregory wrote:

> So now, would the Flume version still matter?
> 
> Gary
> 
> 
> On Sun, Jan 27, 2013 at 8:52 PM, Gary Gregory <ga...@gmail.com> wrote:
> Works for me on Java 7 and 6 on Win 7.
> 
> Gary
> 
> 
> On Sun, Jan 27, 2013 at 8:04 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> Please update and try again.  I was able to get it to fail consistently on a Windows machine my wife has.  I converted the tests to use the memory channel instead of the file channel and they now are working consistently for me.
> 
> Ralph
> 
> On Jan 27, 2013, at 1:34 AM, Ivan Habunek wrote:
> 
> > On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com> wrote:
> >> This is interesting.  Can you a) provide me with information on your
> >> hardware?  The elapsed times below are even slower than my VM.   Also, can
> >> you rerun it and modify embedded.xml and change status="warn" to
> >> status="debug" and change the root logger level to debug as well?
> >
> > Here is a failure with debug logging.
> > http://pastebin.com/raw.php?i=9hvtpENR
> >
> > Regards,
> > Ivan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
I tried 1.3.1 on Windows and although Netty is throwing a "ClosedByInterruptException" all the unit tests are passing. I don't see those exceptions on my Mac.

For the moment I think I will just leave it at 1.2.0.

Ralph

On Jan 27, 2013, at 5:53 PM, Gary Gregory wrote:

> So now, would the Flume version still matter?
> 
> Gary
> 
> 
> On Sun, Jan 27, 2013 at 8:52 PM, Gary Gregory <ga...@gmail.com> wrote:
> Works for me on Java 7 and 6 on Win 7.
> 
> Gary
> 
> 
> On Sun, Jan 27, 2013 at 8:04 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> Please update and try again.  I was able to get it to fail consistently on a Windows machine my wife has.  I converted the tests to use the memory channel instead of the file channel and they now are working consistently for me.
> 
> Ralph
> 
> On Jan 27, 2013, at 1:34 AM, Ivan Habunek wrote:
> 
> > On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com> wrote:
> >> This is interesting.  Can you a) provide me with information on your
> >> hardware?  The elapsed times below are even slower than my VM.   Also, can
> >> you rerun it and modify embedded.xml and change status="warn" to
> >> status="debug" and change the root logger level to debug as well?
> >
> > Here is a failure with debug logging.
> > http://pastebin.com/raw.php?i=9hvtpENR
> >
> > Regards,
> > Ivan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Re: Please test

Posted by Gary Gregory <ga...@gmail.com>.
So now, would the Flume version still matter?

Gary


On Sun, Jan 27, 2013 at 8:52 PM, Gary Gregory <ga...@gmail.com>wrote:

> Works for me on Java 7 and 6 on Win 7.
>
> Gary
>
>
> On Sun, Jan 27, 2013 at 8:04 PM, Ralph Goers <ra...@dslextreme.com>wrote:
>
>> Please update and try again.  I was able to get it to fail consistently
>> on a Windows machine my wife has.  I converted the tests to use the memory
>> channel instead of the file channel and they now are working consistently
>> for me.
>>
>> Ralph
>>
>> On Jan 27, 2013, at 1:34 AM, Ivan Habunek wrote:
>>
>> > On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>> >> This is interesting.  Can you a) provide me with information on your
>> >> hardware?  The elapsed times below are even slower than my VM.   Also,
>> can
>> >> you rerun it and modify embedded.xml and change status="warn" to
>> >> status="debug" and change the root logger level to debug as well?
>> >
>> > Here is a failure with debug logging.
>> > http://pastebin.com/raw.php?i=9hvtpENR
>> >
>> > Regards,
>> > Ivan
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Please test

Posted by Gary Gregory <ga...@gmail.com>.
Works for me on Java 7 and 6 on Win 7.

Gary


On Sun, Jan 27, 2013 at 8:04 PM, Ralph Goers <ra...@dslextreme.com>wrote:

> Please update and try again.  I was able to get it to fail consistently on
> a Windows machine my wife has.  I converted the tests to use the memory
> channel instead of the file channel and they now are working consistently
> for me.
>
> Ralph
>
> On Jan 27, 2013, at 1:34 AM, Ivan Habunek wrote:
>
> > On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >> This is interesting.  Can you a) provide me with information on your
> >> hardware?  The elapsed times below are even slower than my VM.   Also,
> can
> >> you rerun it and modify embedded.xml and change status="warn" to
> >> status="debug" and change the root logger level to debug as well?
> >
> > Here is a failure with debug logging.
> > http://pastebin.com/raw.php?i=9hvtpENR
> >
> > Regards,
> > Ivan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Please test

Posted by Ivan Habunek <iv...@gmail.com>.
On 28 January 2013 02:04, Ralph Goers <ra...@dslextreme.com> wrote:
> Please update and try again.  I was able to get it to fail consistently on a Windows machine my wife has.  I converted the tests to use the memory channel instead of the file channel and they now are working consistently for me.

I ran tests 3 times in a row, and they passed each time. The site
generation passes as well. So that seems to be solved.

BTW, for next release you can ask us to run tests once before creating
an RC to save you the bother in case there are any failures. :)

Regards,
Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
Please update and try again.  I was able to get it to fail consistently on a Windows machine my wife has.  I converted the tests to use the memory channel instead of the file channel and they now are working consistently for me.

Ralph

On Jan 27, 2013, at 1:34 AM, Ivan Habunek wrote:

> On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com> wrote:
>> This is interesting.  Can you a) provide me with information on your
>> hardware?  The elapsed times below are even slower than my VM.   Also, can
>> you rerun it and modify embedded.xml and change status="warn" to
>> status="debug" and change the root logger level to debug as well?
> 
> Here is a failure with debug logging.
> http://pastebin.com/raw.php?i=9hvtpENR
> 
> Regards,
> Ivan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ivan Habunek <iv...@gmail.com>.
On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com> wrote:
> This is interesting.  Can you a) provide me with information on your
> hardware?  The elapsed times below are even slower than my VM.   Also, can
> you rerun it and modify embedded.xml and change status="warn" to
> status="debug" and change the root logger level to debug as well?

Here is a failure with debug logging.
http://pastebin.com/raw.php?i=9hvtpENR

Regards,
Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ivan Habunek <iv...@gmail.com>.
On 27 January 2013 10:16, Ivan Habunek <iv...@gmail.com> wrote:
> I ran tests and got it to succeed once:
> http://pastebin.com/raw.php?i=2dK6bHCq
>
> And fail once:
> http://pastebin.com/raw.php?i=tXC2g4rU

Just to note, both runs were using the same version of Java 1.7.0_07.

Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ivan Habunek <iv...@gmail.com>.
On 27 January 2013 07:34, Ralph Goers <ra...@dslextreme.com> wrote:
> This is interesting.  Can you a) provide me with information on your
> hardware?  The elapsed times below are even slower than my VM.   Also, can
> you rerun it and modify embedded.xml and change status="warn" to
> status="debug" and change the root logger level to debug as well?

I ran tests and got it to succeed once:
http://pastebin.com/raw.php?i=2dK6bHCq

And fail once:
http://pastebin.com/raw.php?i=tXC2g4rU

Do you want me to try with debug level too?

My machine is Intel Core2Duo @ 3 GHz, 4GB RAM, running windows 7 64bit.

Regards
Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
This is interesting.  Can you a) provide me with information on your hardware?  The elapsed times below are even slower than my VM.   Also, can you rerun it and modify embedded.xml and change status="warn" to status="debug" and change the root logger level to debug as well?

Ralph


On Jan 26, 2013, at 6:00 PM, Gary Gregory wrote:

> All is well on Java 6 but on Java 7 it fails:
> 
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.logging.log4j.flume.appender.FlumeAppenderTest
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.102 sec
> Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAgentTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.734 sec
> Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest
> 2013-01-26 20:47:47,094 [WARN] org.apache.flume.sink.FailoverSinkProcessor Sink agent1 failed and has been sent to failover list
> org.apache.flume.EventDeliveryException: Failed to send events
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:325) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:182) [flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient { host: localhost, port: 65365 }: Failed to send batch
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:236) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:309) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         ... 3 more
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient { host: localhost, port: 65365 }: RPC request exception
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:286) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:309) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         ... 3 more
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Error connecting to localhost/127.0.0.1:65365
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262) ~[?:1.7.0_11]
>         at java.util.concurrent.FutureTask.get(FutureTask.java:119) ~[?:1.7.0_11]
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:278) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:309) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         ... 3 more
> Caused by: java.io.IOException: Error connecting to localhost/127.0.0.1:65365
>         at org.apache.avro.ipc.NettyTransceiver.getChannel(NettyTransceiver.java:249) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:364) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.request(Requestor.java:147) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.request(Requestor.java:129) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:68) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at $Proxy18.appendBatch(Unknown Source) ~[?:?]
>         at org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:269) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:265) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) ~[?:1.7.0_11]
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166) ~[?:1.7.0_11]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) ~[?:1.7.0_11]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ~[?:1.7.0_11]
>         ... 1 more
> Caused by: java.net.ConnectException: Connection refused: no further information
>         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.7.0_11]
>         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692) ~[?:1.7.0_11]
>         at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401) ~[netty-3.2.7.Final.jar:?]
>         at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370) ~[netty-3.2.7.Final.jar:?]
>         at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292) ~[netty-3.2.7.Final.jar:?]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) ~[?:1.7.0_11]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ~[?:1.7.0_11]
>         ... 1 more
> 20:47:49.988 [SinkRunner-PollingRunner-FailoverSinkProcessor] ERROR org.apache.flume.SinkRunner - Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> 2013-01-26 20:47:55,086 [ERROR] org.apache.flume.SinkRunner Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> 2013-01-26 20:48:00,185 [ERROR] org.apache.flume.SinkRunner Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> 2013-01-26 20:48:05,186 [ERROR] org.apache.flume.SinkRunner Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> 2013-01-26 20:48:10,283 [ERROR] org.apache.flume.SinkRunner Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> 2013-01-26 20:48:15,284 [ERROR] org.apache.flume.SinkRunner Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> No Event returned
> 2013-01-26 20:48:20,285 [ERROR] org.apache.flume.SinkRunner Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 41.755 sec <<< FAILURE!
> testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)  Time elapsed: 32.038 sec  <<< FAILURE!
> java.lang.AssertionError:
>         at org.junit.Assert.fail(Assert.java:91)
>         at org.junit.Assert.assertTrue(Assert.java:43)
>         at org.junit.Assert.assertNotNull(Assert.java:524)
>         at org.junit.Assert.assertNotNull(Assert.java:535)
>         at org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest.testLog4Event(FlumeEmbeddedAppenderTest.java:133)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>         at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>         at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>         at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>         at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>         at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>         at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>         at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>         at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>         at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>         at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>         at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> 
> 
> Results :
> 
> Failed tests:   testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)
> 
> Tests run: 13, Failures: 1, Errors: 0, Skipped: 0
> 
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.230s]
> [INFO] Apache Log4j API .................................. SUCCESS [8.206s]
> [INFO] Apache Log4J Core ................................. SUCCESS [1:48.064s]
> [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [3.091s]
> [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [1.648s]
> [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [1.747s]
> [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [1.075s]
> [INFO] Apache Log4j Flume NG Bridge ...................... FAILURE [1:16.994s]
> [INFO] Log4j Web Adapters ................................ SKIPPED
> [INFO] log4j-samples ..................................... SKIPPED
> [INFO] flume-common ...................................... SKIPPED
> [INFO] flume-remote ...................................... SKIPPED
> [INFO] flume-embedded .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 3:23.132s
> [INFO] Finished at: Sat Jan 26 20:48:21 EST 2013
> [INFO] Final Memory: 27M/199M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project log4j-flume-ng: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\svn\org\apache\log4j2\trunk\flume-ng\target\surefire-reports for the individual test results.
> [ERROR] -> [Help 1]
> 
> Gary
> 
> 
> On Sat, Jan 26, 2013 at 7:59 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> I have modified the tests again and run them on Windows 7 with Java 7 several times and haven't had them fail.   However I am running Windows in a VM on my Mac and they run considerably slower then they do in OSX.  Could you guys please test again?
> 
> Ralph
> 
> 
> On Jan 23, 2013, at 11:23 PM, Ivan Habunek wrote:
> 
> > On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com> wrote:
> >> After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?
> >
> > I get even more failures than Gary.
> >
> > Log is here:
> > http://pastebin.com/raw.php?i=7LUUSQwD
> >
> > Running on:
> > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> > Maven home: d:\Dev\apache-maven-3.0.4\bin\..
> > Java version: 1.7.0_07, vendor: Oracle Corporation
> > Java home: d:\Dev\Java\jdk1.7.0_07\jre
> > Default locale: en_US, platform encoding: Cp1250
> > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> >
> > Regards,
> > Ivan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Re: Please test

Posted by Gary Gregory <ga...@gmail.com>.
All is well on Java 6 but on Java 7 it fails:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.logging.log4j.flume.appender.FlumeAppenderTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.102 sec
Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAgentTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.734 sec
Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest
2013-01-26 20:47:47,094 [WARN] org.apache.flume.sink.FailoverSinkProcessor
Sink agent1 failed and has been sent to failover list
org.apache.flume.EventDeliveryException: Failed to send events
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:325)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:182)
[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
host: localhost, port: 65365 }: Failed to send batch
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:236)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:309)
~[flume-ng-core-1.2.0.jar:1.2.0]
        ... 3 more
Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
host: localhost, port: 65365 }: RPC request exception
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:286)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:309)
~[flume-ng-core-1.2.0.jar:1.2.0]
        ... 3 more
Caused by: java.util.concurrent.ExecutionException: java.io.IOException:
Error connecting to localhost/127.0.0.1:65365
        at
java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262)
~[?:1.7.0_11]
        at java.util.concurrent.FutureTask.get(FutureTask.java:119)
~[?:1.7.0_11]
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:278)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:309)
~[flume-ng-core-1.2.0.jar:1.2.0]
        ... 3 more
Caused by: java.io.IOException: Error connecting to localhost/
127.0.0.1:65365
        at
org.apache.avro.ipc.NettyTransceiver.getChannel(NettyTransceiver.java:249)
~[avro-ipc-1.6.3.jar:1.6.3]
        at
org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:364)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
~[avro-ipc-1.6.3.jar:1.6.3]
        at
org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.request(Requestor.java:147)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
~[avro-ipc-1.6.3.jar:1.6.3]
        at
org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:68)
~[avro-ipc-1.6.3.jar:1.6.3]
        at $Proxy18.appendBatch(Unknown Source) ~[?:?]
        at
org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:269)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:265)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
~[?:1.7.0_11]
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
~[?:1.7.0_11]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
~[?:1.7.0_11]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
~[?:1.7.0_11]
        ... 1 more
Caused by: java.net.ConnectException: Connection refused: no further
information
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
~[?:1.7.0_11]
        at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
~[?:1.7.0_11]
        at
org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401)
~[netty-3.2.7.Final.jar:?]
        at
org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370)
~[netty-3.2.7.Final.jar:?]
        at
org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292)
~[netty-3.2.7.Final.jar:?]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
~[?:1.7.0_11]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
~[?:1.7.0_11]
        ... 1 more
20:47:49.988 [SinkRunner-PollingRunner-FailoverSinkProcessor] ERROR
org.apache.flume.SinkRunner - Unable to deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
2013-01-26 20:47:55,086 [ERROR] org.apache.flume.SinkRunner Unable to
deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
2013-01-26 20:48:00,185 [ERROR] org.apache.flume.SinkRunner Unable to
deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
2013-01-26 20:48:05,186 [ERROR] org.apache.flume.SinkRunner Unable to
deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
2013-01-26 20:48:10,283 [ERROR] org.apache.flume.SinkRunner Unable to
deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
2013-01-26 20:48:15,284 [ERROR] org.apache.flume.SinkRunner Unable to
deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
No Event returned
2013-01-26 20:48:20,285 [ERROR] org.apache.flume.SinkRunner Unable to
deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 41.755 sec
<<< FAILURE!
testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)
Time elapsed: 32.038 sec  <<< FAILURE!
java.lang.AssertionError:
        at org.junit.Assert.fail(Assert.java:91)
        at org.junit.Assert.assertTrue(Assert.java:43)
        at org.junit.Assert.assertNotNull(Assert.java:524)
        at org.junit.Assert.assertNotNull(Assert.java:535)
        at
org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest.testLog4Event(FlumeEmbeddedAppenderTest.java:133)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
        at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
        at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
        at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
        at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
        at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
        at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
        at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
        at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
        at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


Results :

Failed tests:
testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)

Tests run: 13, Failures: 1, Errors: 0, Skipped: 0

[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 .................................... SUCCESS [1.230s]
[INFO] Apache Log4j API .................................. SUCCESS [8.206s]
[INFO] Apache Log4J Core ................................. SUCCESS
[1:48.064s]
[INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [3.091s]
[INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [1.648s]
[INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [1.747s]
[INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [1.075s]
[INFO] Apache Log4j Flume NG Bridge ...................... FAILURE
[1:16.994s]
[INFO] Log4j Web Adapters ................................ SKIPPED
[INFO] log4j-samples ..................................... SKIPPED
[INFO] flume-common ...................................... SKIPPED
[INFO] flume-remote ...................................... SKIPPED
[INFO] flume-embedded .................................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3:23.132s
[INFO] Finished at: Sat Jan 26 20:48:21 EST 2013
[INFO] Final Memory: 27M/199M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
on project log4j-flume-ng: There are test failures.
[ERROR]
[ERROR] Please refer to
C:\svn\org\apache\log4j2\trunk\flume-ng\target\surefire-reports for the
individual test results.
[ERROR] -> [Help 1]

Gary


On Sat, Jan 26, 2013 at 7:59 PM, Ralph Goers <ra...@dslextreme.com>wrote:

> I have modified the tests again and run them on Windows 7 with Java 7
> several times and haven't had them fail.   However I am running Windows in
> a VM on my Mac and they run considerably slower then they do in OSX.  Could
> you guys please test again?
>
> Ralph
>
>
> On Jan 23, 2013, at 11:23 PM, Ivan Habunek wrote:
>
> > On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >> After testing for quite a bit it appears that Flume 1.3.1 is not
> terminating some threads during shutdown and they are causing the
> checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0
> and the tests pass again for me on Windows.  Could you please test on
> Windows to verify that I can go ahead with another rc?
> >
> > I get even more failures than Gary.
> >
> > Log is here:
> > http://pastebin.com/raw.php?i=7LUUSQwD
> >
> > Running on:
> > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> > Maven home: d:\Dev\apache-maven-3.0.4\bin\..
> > Java version: 1.7.0_07, vendor: Oracle Corporation
> > Java home: d:\Dev\Java\jdk1.7.0_07\jre
> > Default locale: en_US, platform encoding: Cp1250
> > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> >
> > Regards,
> > Ivan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
I have modified the tests again and run them on Windows 7 with Java 7 several times and haven't had them fail.   However I am running Windows in a VM on my Mac and they run considerably slower then they do in OSX.  Could you guys please test again?

Ralph


On Jan 23, 2013, at 11:23 PM, Ivan Habunek wrote:

> On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com> wrote:
>> After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?
> 
> I get even more failures than Gary.
> 
> Log is here:
> http://pastebin.com/raw.php?i=7LUUSQwD
> 
> Running on:
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: d:\Dev\apache-maven-3.0.4\bin\..
> Java version: 1.7.0_07, vendor: Oracle Corporation
> Java home: d:\Dev\Java\jdk1.7.0_07\jre
> Default locale: en_US, platform encoding: Cp1250
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> 
> Regards,
> Ivan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ralph Goers <rg...@apache.org>.
All log4j2 tests are already run in a separate vm. They have to be given hoe initialization & configuration works.

At this point I'm not sure where the problem lies. My guess is that there are delays sine the flume sink gets the data a synchronously from the channel and the another delay when the sink sends the data over tcp to the tests source. So the test may be trying to remove from its channel before it has arrived.  I've tried adding a short sleep interval but the error still occurs.

Sent from my iPad

On Jan 24, 2013, at 3:33 AM, Gary Gregory <ga...@gmail.com> wrote:

> Is this a Flume bug or a problem with how we use/reuse Flume from test to test. Would it help to run each test class in a separate JVM? Or would that hide a genuine problem?
> 
> Gary
> 
> 
> On Thu, Jan 24, 2013 at 2:34 AM, Ralph Goers <ra...@dslextreme.com> wrote:
>> Thanks.  That makes sense since the 2 failing tests are essentially the same except they configure the embedded appender differently.
>> 
>> Ralph
>> 
>> On Jan 23, 2013, at 11:23 PM, Ivan Habunek wrote:
>> 
>> > On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com> wrote:
>> >> After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?
>> >
>> > I get even more failures than Gary.
>> >
>> > Log is here:
>> > http://pastebin.com/raw.php?i=7LUUSQwD
>> >
>> > Running on:
>> > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
>> > Maven home: d:\Dev\apache-maven-3.0.4\bin\..
>> > Java version: 1.7.0_07, vendor: Oracle Corporation
>> > Java home: d:\Dev\Java\jdk1.7.0_07\jre
>> > Default locale: en_US, platform encoding: Cp1250
>> > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>> >
>> > Regards,
>> > Ivan
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

Re: Please test

Posted by Gary Gregory <ga...@gmail.com>.
Is this a Flume bug or a problem with how we use/reuse Flume from test to
test. Would it help to run each test class in a separate JVM? Or would that
hide a genuine problem?

Gary


On Thu, Jan 24, 2013 at 2:34 AM, Ralph Goers <ra...@dslextreme.com>wrote:

> Thanks.  That makes sense since the 2 failing tests are essentially the
> same except they configure the embedded appender differently.
>
> Ralph
>
> On Jan 23, 2013, at 11:23 PM, Ivan Habunek wrote:
>
> > On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >> After testing for quite a bit it appears that Flume 1.3.1 is not
> terminating some threads during shutdown and they are causing the
> checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0
> and the tests pass again for me on Windows.  Could you please test on
> Windows to verify that I can go ahead with another rc?
> >
> > I get even more failures than Gary.
> >
> > Log is here:
> > http://pastebin.com/raw.php?i=7LUUSQwD
> >
> > Running on:
> > Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> > Maven home: d:\Dev\apache-maven-3.0.4\bin\..
> > Java version: 1.7.0_07, vendor: Oracle Corporation
> > Java home: d:\Dev\Java\jdk1.7.0_07\jre
> > Default locale: en_US, platform encoding: Cp1250
> > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> >
> > Regards,
> > Ivan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks.  That makes sense since the 2 failing tests are essentially the same except they configure the embedded appender differently.

Ralph

On Jan 23, 2013, at 11:23 PM, Ivan Habunek wrote:

> On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com> wrote:
>> After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?
> 
> I get even more failures than Gary.
> 
> Log is here:
> http://pastebin.com/raw.php?i=7LUUSQwD
> 
> Running on:
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: d:\Dev\apache-maven-3.0.4\bin\..
> Java version: 1.7.0_07, vendor: Oracle Corporation
> Java home: d:\Dev\Java\jdk1.7.0_07\jre
> Default locale: en_US, platform encoding: Cp1250
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> 
> Regards,
> Ivan
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ivan Habunek <iv...@gmail.com>.
On 24 January 2013 02:15, Ralph Goers <ra...@dslextreme.com> wrote:
> After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?

I get even more failures than Gary.

Log is here:
http://pastebin.com/raw.php?i=7LUUSQwD

Running on:
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: d:\Dev\apache-maven-3.0.4\bin\..
Java version: 1.7.0_07, vendor: Oracle Corporation
Java home: d:\Dev\Java\jdk1.7.0_07\jre
Default locale: en_US, platform encoding: Cp1250
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

Regards,
Ivan

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Re: Please test

Posted by Ralph Goers <ra...@dslextreme.com>.
Interesting. I ran it once with Java 7 and it passed. I ran it again and it failed with the same error you got so it appears there is a timing error.

Ralph

On Jan 23, 2013, at 5:45 PM, Gary Gregory wrote:

> On Wed, Jan 23, 2013 at 8:15 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> After testing for quite a bit it appears that Flume 1.3.1 is not terminating some threads during shutdown and they are causing the checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0 and the tests pass again for me on Windows.  Could you please test on Windows to verify that I can go ahead with another rc?
> 
> 
> The tests with the latest from trunk all pass with "mvn test" on:
> 
> Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_38, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_38\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> 
> but then with Java 1.7.0_11 I get an error:
> 
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.logging.log4j.flume.appender.FlumeAppenderTest
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.692 sec
> Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAgentTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.865 sec
> Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest
> 2013-01-23 20:44:13,494 [WARN] org.apache.flume.sink.FailoverSinkProcessor Sink agent1 failed and has been sent to failover list
> org.apache.flume.EventDeliveryException: Failed to send events
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:325) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:182) [flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient { host: localhost, port: 12345 }: Failed to send batch
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:236) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:309) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         ... 3 more
> Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient { host: localhost, port: 12345 }: RPC request exception
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:286) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:309) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         ... 3 more
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Error connecting to localhost/127.0.0.1:12345
>         at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262) ~[?:1.7.0_11]
>         at java.util.concurrent.FutureTask.get(FutureTask.java:119) ~[?:1.7.0_11]
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:278) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.sink.AvroSink.process(AvroSink.java:309) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         ... 3 more
> Caused by: java.io.IOException: Error connecting to localhost/127.0.0.1:12345
>         at org.apache.avro.ipc.NettyTransceiver.getChannel(NettyTransceiver.java:249) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:364) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.request(Requestor.java:147) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.Requestor.request(Requestor.java:129) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:68) ~[avro-ipc-1.6.3.jar:1.6.3]
>         at $Proxy18.appendBatch(Unknown Source) ~[?:?]
>         at org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:269) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:265) ~[flume-ng-sdk-1.2.0.jar:1.2.0]
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) ~[?:1.7.0_11]
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166) ~[?:1.7.0_11]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) ~[?:1.7.0_11]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ~[?:1.7.0_11]
>         ... 1 more
> Caused by: java.net.ConnectException: Connection refused: no further information
>         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.7.0_11]
>         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692) ~[?:1.7.0_11]
>         at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401) ~[netty-3.2.7.Final.jar:?]
>         at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370) ~[netty-3.2.7.Final.jar:?]
>         at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292) ~[netty-3.2.7.Final.jar:?]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) ~[?:1.7.0_11]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ~[?:1.7.0_11]
>         ... 1 more
> 20:44:16.493 [SinkRunner-PollingRunner-FailoverSinkProcessor] ERROR org.apache.flume.SinkRunner - Unable to deliver event. Exception follows.
> org.apache.flume.EventDeliveryException: All sinks failed to process, nothing left to failover to
>         at org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191) ~[flume-ng-core-1.2.0.jar:1.2.0]
>         at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) [flume-ng-core-1.2.0.jar:1.2.0]
>         at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.521 sec <<< FAILURE!
> testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)  Time elapsed: 5.151 sec  <<< FAILURE!
> java.lang.AssertionError:
>         at org.junit.Assert.fail(Assert.java:91)
>         at org.junit.Assert.assertTrue(Assert.java:43)
>         at org.junit.Assert.assertNotNull(Assert.java:524)
>         at org.junit.Assert.assertNotNull(Assert.java:535)
>         at org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest.testLog4Event(FlumeEmbeddedAppenderTest.java:180)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>         at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>         at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>         at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>         at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
>         at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>         at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>         at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>         at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>         at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>         at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>         at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>         at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>         at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>         at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>         at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>         at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> 
> 
> Results :
> 
> Failed tests:   testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)
> 
> Tests run: 13, Failures: 1, Errors: 0, Skipped: 0
> 
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.348s]
> [INFO] Apache Log4j API .................................. SUCCESS [9.815s]
> [INFO] Apache Log4J Core ................................. SUCCESS [1:48.865s]
> [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [2.388s]
> [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [2.089s]
> [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [1.559s]
> [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [1.105s]
> [INFO] Apache Log4j Flume NG Bridge ...................... FAILURE [49.804s]
> [INFO] Log4j Web Adapters ................................ SKIPPED
> [INFO] log4j-samples ..................................... SKIPPED
> [INFO] flume-common ...................................... SKIPPED
> [INFO] flume-remote ...................................... SKIPPED
> [INFO] flume-embedded .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2:58.516s
> [INFO] Finished at: Wed Jan 23 20:44:20 EST 2013
> [INFO] Final Memory: 30M/186M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project log4j-flume-ng: There are test failures.
> [ERROR]
> 
> Gary
>  
> Thanks,
> Ralph
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 
> 
> 
> 
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Re: Please test

Posted by Gary Gregory <ga...@gmail.com>.
On Wed, Jan 23, 2013 at 8:15 PM, Ralph Goers <ra...@dslextreme.com>wrote:

> After testing for quite a bit it appears that Flume 1.3.1 is not
> terminating some threads during shutdown and they are causing the
> checkpoint files to not be able to be deleted.  I reverted to Flume 1.2.0
> and the tests pass again for me on Windows.  Could you please test on
> Windows to verify that I can go ahead with another rc?
>
>
The tests with the latest from trunk all *pass *with "mvn test" on:

Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Maven home: C:\Java\apache-maven-3.0.4\bin\..
Java version: *1.6.0_38*, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_38\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

but then with Java *1.7.0_11* I get an error:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.logging.log4j.flume.appender.FlumeAppenderTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.692 sec
Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAgentTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.865 sec
Running org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest
2013-01-23 20:44:13,494 [WARN] org.apache.flume.sink.FailoverSinkProcessor
Sink agent1 failed and has been sent to failover list
org.apache.flume.EventDeliveryException: Failed to send events
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:325)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:182)
[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
host: localhost, port: 12345 }: Failed to send batch
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:236)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:309)
~[flume-ng-core-1.2.0.jar:1.2.0]
        ... 3 more
Caused by: org.apache.flume.EventDeliveryException: NettyAvroRpcClient {
host: localhost, port: 12345 }: RPC request exception
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:286)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:309)
~[flume-ng-core-1.2.0.jar:1.2.0]
        ... 3 more
Caused by: java.util.concurrent.ExecutionException: java.io.IOException:
Error connecting to localhost/127.0.0.1:12345
        at
java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262)
~[?:1.7.0_11]
        at java.util.concurrent.FutureTask.get(FutureTask.java:119)
~[?:1.7.0_11]
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:278)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
org.apache.flume.api.NettyAvroRpcClient.appendBatch(NettyAvroRpcClient.java:224)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at org.apache.flume.sink.AvroSink.process(AvroSink.java:309)
~[flume-ng-core-1.2.0.jar:1.2.0]
        ... 3 more
Caused by: java.io.IOException: Error connecting to localhost/
127.0.0.1:12345
        at
org.apache.avro.ipc.NettyTransceiver.getChannel(NettyTransceiver.java:249)
~[avro-ipc-1.6.3.jar:1.6.3]
        at
org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:364)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
~[avro-ipc-1.6.3.jar:1.6.3]
        at
org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.request(Requestor.java:147)
~[avro-ipc-1.6.3.jar:1.6.3]
        at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
~[avro-ipc-1.6.3.jar:1.6.3]
        at
org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:68)
~[avro-ipc-1.6.3.jar:1.6.3]
        at $Proxy18.appendBatch(Unknown Source) ~[?:?]
        at
org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:269)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
org.apache.flume.api.NettyAvroRpcClient$2.call(NettyAvroRpcClient.java:265)
~[flume-ng-sdk-1.2.0.jar:1.2.0]
        at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
~[?:1.7.0_11]
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
~[?:1.7.0_11]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
~[?:1.7.0_11]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
~[?:1.7.0_11]
        ... 1 more
Caused by: java.net.ConnectException: Connection refused: no further
information
        at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
~[?:1.7.0_11]
        at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)
~[?:1.7.0_11]
        at
org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.connect(NioClientSocketPipelineSink.java:401)
~[netty-3.2.7.Final.jar:?]
        at
org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processSelectedKeys(NioClientSocketPipelineSink.java:370)
~[netty-3.2.7.Final.jar:?]
        at
org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:292)
~[netty-3.2.7.Final.jar:?]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
~[?:1.7.0_11]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
~[?:1.7.0_11]
        ... 1 more
20:44:16.493 [SinkRunner-PollingRunner-FailoverSinkProcessor] ERROR
org.apache.flume.SinkRunner - Unable to deliver event. Exception follows.
org.apache.flume.EventDeliveryException: All sinks failed to process,
nothing left to failover to
        at
org.apache.flume.sink.FailoverSinkProcessor.process(FailoverSinkProcessor.java:191)
~[flume-ng-core-1.2.0.jar:1.2.0]
        at
org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147)
[flume-ng-core-1.2.0.jar:1.2.0]
        at java.lang.Thread.run(Thread.java:722) [?:1.7.0_11]
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.521 sec
<<< FAILURE!
testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)
Time elapsed: 5.151 sec  <<< FAILURE!
java.lang.AssertionError:
        at org.junit.Assert.fail(Assert.java:91)
        at org.junit.Assert.assertTrue(Assert.java:43)
        at org.junit.Assert.assertNotNull(Assert.java:524)
        at org.junit.Assert.assertNotNull(Assert.java:535)
        at
org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest.testLog4Event(FlumeEmbeddedAppenderTest.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
        at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
        at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
        at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
        at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
        at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
        at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
        at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
        at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
        at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)


Results :

Failed tests:
testLog4Event(org.apache.logging.log4j.flume.appender.FlumeEmbeddedAppenderTest)

Tests run: 13, Failures: 1, Errors: 0, Skipped: 0

[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 .................................... SUCCESS [1.348s]
[INFO] Apache Log4j API .................................. SUCCESS [9.815s]
[INFO] Apache Log4J Core ................................. SUCCESS
[1:48.865s]
[INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [2.388s]
[INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [2.089s]
[INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [1.559s]
[INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [1.105s]
[INFO] Apache Log4j Flume NG Bridge ...................... FAILURE [49.804s]
[INFO] Log4j Web Adapters ................................ SKIPPED
[INFO] log4j-samples ..................................... SKIPPED
[INFO] flume-common ...................................... SKIPPED
[INFO] flume-remote ...................................... SKIPPED
[INFO] flume-embedded .................................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 2:58.516s
[INFO] Finished at: Wed Jan 23 20:44:20 EST 2013
[INFO] Final Memory: 30M/186M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test)
on project log4j-flume-ng: There are test failures.
[ERROR]

Gary


> Thanks,
> Ralph
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory