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

Inder SIngh commented on FLUME-1271:
------------------------------------

The bigger question to ask is -> since FLUME is highly configurable, validation 
of the FLUME CFG and reporting exact errors would help in OPS to maintain FLUME 
based systems.
                
> Incorrect configuration causes NPE
> ----------------------------------
>
>                 Key: FLUME-1271
>                 URL: https://issues.apache.org/jira/browse/FLUME-1271
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: v1.1.0
>            Reporter: Inder SIngh
>            Priority: Trivial
>
> Problem Description
> ---------------------
> An incorrect configuration something like below can result in NPE in FLUME.
> agent1.sources.seqsource.type=seq
> #agent1.sources.seqsource.channels=ch1
> Exception Details
> -----------------
> 2012-06-11 15:08:28,748 ERROR properties.PropertiesFileConfigurationProvider: 
> Failed to load configuration data. Exception follows.
> java.lang.NullPointerException
>         at 
> org.apache.flume.conf.properties.PropertiesFileConfigurationProvider.loadSources(PropertiesFileConfigurationProvider.java:324)
>         at 
> org.apache.flume.conf.properties.PropertiesFileConfigurationProvider.load(PropertiesFileConfigurationProvider.java:222)
>         at 
> org.apache.flume.conf.file.AbstractFileConfigurationProvider.doLoad(AbstractFileConfigurationProvider.java:123)
>         at 
> org.apache.flume.conf.file.AbstractFileConfigurationProvider.access$300(AbstractFileConfigurationProvider.java:38)
> Cause
> ------
> PropertiesFileConfigurationProvider->loadSources() {
> ...
> ...
> String[] channelNames = context.getString(
>             BasicConfigurationConstants.CONFIG_CHANNELS).split("\\s+");
> ...
> }

--
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

        

Reply via email to