You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Will McQueen (Closed) (JIRA)" <ji...@apache.org> on 2011/11/22 02:48:40 UTC

[jira] [Closed] (FLUME-844) jdbc channel fails with seq source and logger sink

     [ https://issues.apache.org/jira/browse/FLUME-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will McQueen closed FLUME-844.
------------------------------

    
> jdbc channel fails with seq source and logger sink
> --------------------------------------------------
>
>                 Key: FLUME-844
>                 URL: https://issues.apache.org/jira/browse/FLUME-844
>             Project: Flume
>          Issue Type: Bug
>         Environment: Using flume-728 branch, commit object 0014756b8462ed2711d2e3af4ccabcabff4fdc70
> flume.properties file contents:
> host1.channels = jdbcChannel
> host1.sources = seqSource
> host1.sinks = loggerSink
> #
> host1.channels.jdbcChannel.type=jdbc
> #
> host1.sources.seqSource.type=seq
> host1.sources.seqSource.channels=jdbcChannel
> #
> host1.sinks.loggerSink.type=logger
> host1.sinks.loggerSink.channel=jdbcChannel
>            Reporter: Will McQueen
>            Assignee: Arvind Prabhakar
>
> Running a flume node with the above properties file fails with "Failed to load configuration data". There are no problems when using the memory channel instead of jdbc.
> 2011-11-07 11:56:29,767 (conf-file-poller-0) [ERROR - org.apache.flume.conf.file.AbstractFileConfigurationProvider$FileWatcherRunnable.run(AbstractFileConfigurationProvider.java:205)] Failed to load configuration data. Exception follows.
> java.lang.NullPointerException
> 	at org.apache.flume.channel.jdbc.impl.DerbySchemaHandler.schemaExists(DerbySchemaHandler.java:321)
> 	at org.apache.flume.channel.jdbc.impl.JdbcChannelProviderImpl.initializeSchema(JdbcChannelProviderImpl.java:108)
> 	at org.apache.flume.channel.jdbc.impl.JdbcChannelProviderImpl.initialize(JdbcChannelProviderImpl.java:95)
> 	at org.apache.flume.channel.jdbc.JdbcChannelProviderFactory.getProvider(JdbcChannelProviderFactory.java:35)
> 	at org.apache.flume.channel.jdbc.JdbcChannel.configure(JdbcChannel.java:81)
> 	at org.apache.flume.conf.Configurables.configure(Configurables.java:22)
> 	at org.apache.flume.conf.properties.PropertiesFileConfigurationProvider.loadChannels(PropertiesFileConfigurationProvider.java:223)
> 	at org.apache.flume.conf.properties.PropertiesFileConfigurationProvider.load(PropertiesFileConfigurationProvider.java:184)
> 	at org.apache.flume.conf.file.AbstractFileConfigurationProvider.doLoad(AbstractFileConfigurationProvider.java:124)
> 	at org.apache.flume.conf.file.AbstractFileConfigurationProvider.access$1(AbstractFileConfigurationProvider.java:114)
> 	at org.apache.flume.conf.file.AbstractFileConfigurationProvider$FileWatcherRunnable.run(AbstractFileConfigurationProvider.java:203)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)

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