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

Hudson commented on FLUME-2359:
-------------------------------

SUCCESS: Integrated in flume-trunk #639 (See 
[https://builds.apache.org/job/flume-trunk/639/])
FLUME-2359. Update CHANGELOG to include FLUME-2400 (harishreedharan: 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=3708063ef740803f62e61d52bd3ba6e2a94d7c3e)
* CHANGELOG


> TestFileChannelIntegrityTool throws exception on class teardown on Windows
> --------------------------------------------------------------------------
>
>                 Key: FLUME-2359
>                 URL: https://issues.apache.org/jira/browse/FLUME-2359
>             Project: Flume
>          Issue Type: Bug
>          Components: File Channel, Test
>    Affects Versions: v1.4.0
>            Reporter: Roshan Naik
>            Assignee: Roshan Naik
>              Labels: windows
>         Attachments: FLUME-2359.patch
>
>
> Exception is due to inability to delete checkpoint directory. Since there are 
> memory mapped files there, this directory cannot be deleted from within the 
> VM.
> {code}
> java.io.IOException: Unable to delete file: 
> D:\tmp\flume-baikal-GA-1.4.0\1397096136128-0\chkpt\checkpoint_1397096136398
>       at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1919)
>       at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1399)
>       at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1331)
>       at 
> org.apache.flume.tools.TestFileChannelIntegrityTool.tearDownClass(TestFileChannelIntegrityTool.java:98)
>       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:45)
>       at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>       at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>       at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36)
>       at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>       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)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to