db.enabled property causing bean util.DatabaseReferenceRemovingPostProcessor to fail on startup

sgouin

Hi all,

 

Running on LS 7.3.2 on Windows 2k8R2 on Weblogic 10.3.6... trying to get our Livesite app up and running, but failing on startup. Logs reveal the following error:

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'util.DatabaseReferenceRemovingPostProcessor' defined in ServletContext resource [/WEB-INF/conf/livesite/resources/resource-config.xml]: Cannot resolve reference to bean 'db.Enabled' while setting bean property 'condition'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'db.Enabled' defined in ServletContext resource [/WEB-INF/conf/livesite/resources/resource-config.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [boolean]: Could not convert constructor argument value of type [java.lang.String] to required type [boolean]: Failed to convert value of type 'java.lang.String' to required type 'boolean'; nested exception is java.lang.IllegalArgumentException: Invalid boolean value [${db.enabled}]
Related cause: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'db.Enabled' defined in ServletContext resource [/WEB-INF/conf/livesite/resources/resource-config.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [java.lang.String]: Ambiguous constructor argument types - did you specify the correct bean references as constructor arguments?

Our database.properties has the db.enabled=false set...

 

We also have the following in the resource-config.xml file:

 

<bean id="db.Enabled" class="java.lang.Boolean">
    <constructor-arg type="boolean" value="${db.enabled}"/>
  </bean>

<!-- disables all database references when database is disabled. -->
  <bean id="util.DatabaseReferenceRemovingPostProcessor"
        class="com.interwoven.livesite.spring.beans.factory.config.ConditionalReferenceRemovingPostProcessor">
    <property name="condition" ref="db.Enabled"/>
    <property name="removalCondition" value="false" />
    <property name="beanIds">
      <set>
        <!-- <value>dao.DataAccessObjectFactory</value> -->
        <value>db.DataSource</value>
        <value>db.PoolFactory</value>
        <value>db.DefaultPoolFactory</value>
        <value>db.TransactionManager</value>
        <value>development.db.DataSource</value>
        <value>development.hibernate.SessionFactory</value>
        <value>development.db.TransactionManager</value>
        <value>development.dao.TransactionAdvice</value>
        <value>hibernate.SessionFactory</value>
        <value>production.db.DataSource</value>
        <value>production.hibernate.SessionFactory</value>
        <value>production.db.TransactionManager</value>
        <value>production.dao.TransactionAdvice</value>
      </set>
    </property>
  </bean>

 

any ideas on where to look further?

Rick Poulin

${db.enabled} isn't being resolved to its value, which means one of a couple possibilities:

* your database.properties file is not in the /WEB-INF/conf/livesite_customer folder

* WL doesn't have rights to read that file

* there's a character encoding or whitespace issue in the file itself

* the property files loader bean in /WEB-INF/conf/livesite/resources/resource-config.xml is broken or missing

* WL's deployed application root isn't pointing to where you think

 

Knowing WL, the last point is the most likely one. You probably deployed your app from Interwoven\LiveSiteDisplayServices\runtime\web, but that's not where it's actually running from. WL will make a copy of that in some deeply-nested folder structure that looks something like X:\ora11g\WL\some-virtual-server-stuff\some-app-name\stage\stage\magictoken\. That's the copy of database.properties you want to be verifying.