[
https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502060#comment-13502060
]
Yanbo Liang commented on HADOOP-9041:
-------------------------------------
@Radim, in maven+junit test case may not fail is not caused by reduplicative
initialization. Because if reduplicative initialization occur, it will throw
Error.
As my opinion, it caused by the maven+junit framework has load the
implementation of FileSystem before the test case running, so it will call
ServiceLoader ahead of registering FsUrlStreamHandlerFactory all the time.
So the test case can not reproduce in maven+junit.
> FileSystem initialization can go into infinite loop
> ---------------------------------------------------
>
> Key: HADOOP-9041
> URL: https://issues.apache.org/jira/browse/HADOOP-9041
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.2-alpha
> Reporter: Radim Kolar
> Assignee: Yanbo Liang
> Priority: Critical
> Attachments: fsinit-unit.txt, fstest.groovy, HADOOP-9041.patch,
> HADOOP-9041.patch
>
>
> More information is there: https://jira.springsource.org/browse/SHDP-111
> Referenced source code from example is:
> https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java
> from isolating that cause it looks like if you register:
> org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling
> FileSystem.loadFileSystems() then it goes into infinite loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
