[
https://issues.apache.org/jira/browse/OODT-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229989#comment-13229989
]
Brian Foster edited comment on OODT-412 at 3/15/12 8:43 AM:
------------------------------------------------------------
Just figured i'd put this here since it is kinda relavant, when you get errors
on the command-line when using a component using cas-cli you can add:
{code}
-Dorg.apache.oodt.cas.cli.debug=true
{code}
to your components bin script and it will print out the stack trace to
stdout... for example, the error in this issue would be expanded to:
{code}
Exception in thread "main" java.lang.RuntimeException:
org.springframework.beans.factory.BeanInitializationException: Could not
process key 'MoveMetadataToFailureDir.toDir' in PropertyOverrideConfigurer;
nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named
'MoveMetadataToFailureDir' is defined
at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:191)
at
org.apache.oodt.cas.crawl.CrawlerLauncher.main(CrawlerLauncher.java:36)
Caused by: org.springframework.beans.factory.BeanInitializationException: Could
not process key 'MoveMetadataToFailureDir.toDir' in PropertyOverrideConfigurer;
nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named
'MoveMetadataToFailureDir' is defined
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.processProperties(PropertyOverrideConfigurer.java:104)
at
org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:75)
at
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:554)
at
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:528)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:363)
at
org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:140)
at
org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:84)
at
org.apache.oodt.cas.crawl.cli.action.CrawlerLauncherCliAction.execute(CrawlerLauncherCliAction.java:47)
at
org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:331)
at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:187)
... 1 more
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No
bean named 'MoveMetadataToFailureDir' is defined
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:387)
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.applyPropertyValue(PropertyOverrideConfigurer.java:139)
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.processKey(PropertyOverrideConfigurer.java:127)
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.processProperties(PropertyOverrideConfigurer.java:99)
... 10 more
{code}
was (Author: bfoster):
Just figured i'd put this here since it is kinda relavant, when you get
errors on the command-line when using a component using cas-cli you can add:
{code}
-Dorg.apache.oodt.cas.cli.debug=true
{code}
to your components java script and it will print out the stack trace to
stdout... for example, the error in this issue would be expanded to:
{code}
Exception in thread "main" java.lang.RuntimeException:
org.springframework.beans.factory.BeanInitializationException: Could not
process key 'MoveMetadataToFailureDir.toDir' in PropertyOverrideConfigurer;
nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named
'MoveMetadataToFailureDir' is defined
at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:191)
at
org.apache.oodt.cas.crawl.CrawlerLauncher.main(CrawlerLauncher.java:36)
Caused by: org.springframework.beans.factory.BeanInitializationException: Could
not process key 'MoveMetadataToFailureDir.toDir' in PropertyOverrideConfigurer;
nested exception is
org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named
'MoveMetadataToFailureDir' is defined
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.processProperties(PropertyOverrideConfigurer.java:104)
at
org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:75)
at
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:554)
at
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:528)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:363)
at
org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:140)
at
org.springframework.context.support.FileSystemXmlApplicationContext.<init>(FileSystemXmlApplicationContext.java:84)
at
org.apache.oodt.cas.crawl.cli.action.CrawlerLauncherCliAction.execute(CrawlerLauncherCliAction.java:47)
at
org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:331)
at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:187)
... 1 more
Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No
bean named 'MoveMetadataToFailureDir' is defined
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:387)
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.applyPropertyValue(PropertyOverrideConfigurer.java:139)
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.processKey(PropertyOverrideConfigurer.java:127)
at
org.springframework.beans.factory.config.PropertyOverrideConfigurer.processProperties(PropertyOverrideConfigurer.java:99)
... 10 more
{code}
> Bug in cmd-line-options.xml: change MoveMetadataToFailureDir to
> MoveMetadataFileToFailureDir
> --------------------------------------------------------------------------------------------
>
> Key: OODT-412
> URL: https://issues.apache.org/jira/browse/OODT-412
> Project: OODT
> Issue Type: Bug
> Components: crawler
> Affects Versions: 0.4
> Reporter: Thomas Bennett
> Priority: Minor
> Labels: patch
> Fix For: 0.4
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When setting the command line option --failureDir, the command line returns
> the following:
> ERROR: Could not process key 'MoveMetadataToFailureDir.toDir' in
> PropertyOverrideConfigurer; nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
> named 'MoveMetadataToFailureDir' is defined
> Change MoveMetadataToFailureDir (without 'File) to
> MoveMetadataFileToFailureDir
--
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
