Archiva

Failing to startup due to invalid bean definition

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Not A Bug
  • Affects Version/s: 1.1
  • Fix Version/s: 1.1.2
  • Component/s: Web Interface
  • Labels:
    None
  • Environment:
    Tomcat 5.5, Windows, Archiva 1.1
  • Number of attachments :
    0

Description

After doing a war install, running Tomcat yields the following exception:

org.springframework.beans.factory.BeanDefinitionStoreException: Invalid bean definition with name 'archivaConfiguration' defined in null: Could not resolve placeholder 'appserver.base'
at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:252)
at org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:75)
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:542)
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:516)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:348)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3727)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4162)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:603)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:535)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1118)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1020)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)

Issue Links

This issue is depended upon by:
MRM-1085 CLONE -Failing to startup due to invalid bean definition Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

are you specifying the appserver.base system property as described in http://archiva.apache.org/docs/1.1//adminguide/webapp.html?

Show
Brett Porter added a comment - are you specifying the appserver.base system property as described in http://archiva.apache.org/docs/1.1//adminguide/webapp.html?
Hide
Permalink
Michael Mallete added a comment -

yup. they're there. had an archiva 1.0.2 setup in that machine previously on the same tomcat server. cleaned up everything though before installing 1.1: deleted database and repo directories and .m2/archiva*. environment variables preserved.

was able to make it to work now by commenting out propertyPlaceholder in application context xml

Show
Michael Mallete added a comment - yup. they're there. had an archiva 1.0.2 setup in that machine previously on the same tomcat server. cleaned up everything though before installing 1.1: deleted database and repo directories and .m2/archiva*. environment variables preserved. was able to make it to work now by commenting out propertyPlaceholder in application context xml
Hide
Permalink
Maria Odea Ching added a comment -

I tried replicating this but after setting export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" before starting Archiva, the error no longer showed up...

Show
Maria Odea Ching added a comment - I tried replicating this but after setting export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" before starting Archiva, the error no longer showed up...
Hide
Permalink
Maria Odea Ching added a comment -

Closing this as 'Not A Bug' since by settings this --> export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" as specified in the admin guide (when installing Archiva as a war) removes the error. I verified this both with Tomcat 5.5.17 and 6.0.14.. Thanks.

Show
Maria Odea Ching added a comment - Closing this as 'Not A Bug' since by settings this --> export CATALINA_OPTS="-Dappserver.home=$CATALINA_HOME -Dappserver.base=$CATALINA_HOME" as specified in the admin guide (when installing Archiva as a war) removes the error. I verified this both with Tomcat 5.5.17 and 6.0.14.. Thanks.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.