Uploaded image for project: '[Read Only] - Hippo Site Toolkit 2'
  1. [Read Only] - Hippo Site Toolkit 2
  2. HSTTWO-2335

SpringComponent manager reload logs error about ehcache

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • 2.25.05
    • 2.25.05
    • None
    • None

    Description

      The component manager is reloaded when the hst-config.properties file is changed or touched. However, the reload recently started to log en error about EHCache. It is not entirely clear whether the whole reload succeeds or not.

      Steps to reproduce:
      1. start the archetype website
      2. touch the hst-config.properties file:
      touch ./target/tomcat6x/webapps/site/WEB-INF/hst-config.properties

      Expected result: the component manager is reloaded
      Actual result: the component manager tries to reload, but fails with the following error message:

      [INFO] [talledLocalContainer] 02.11.2012 09:29:26 WARN [org.hippoecm.hst.site.container.HstSiteConfigServlet$1.reloadingPerformed():248] HstSiteConfigServlet is trying to reinitialize component manager on configuration change.
      [INFO] [talledLocalContainer] 02.11.2012 09:29:27 ERROR [org.hippoecm.hst.site.container.HstSiteConfigServlet.initializeComponentManager():368] HstSiteConfigServlet: ComponentManager initialization failed.
      [INFO] [talledLocalContainer] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ehCacheManager' defined in class path resource [org/hippoecm/hst/site/container/SpringComponentManager-cache.xml]: Invocation of init method failed; nested exception is net.sf.ehcache.CacheException: Another unnamed CacheManager already exists in the same VM. Please provide unique names for each CacheManager in the config or do one of following:
      [INFO] [talledLocalContainer] 1. Use one of the CacheManager.create() static factory methods to reuse same CacheManager with same name or create one if necessary
      [INFO] [talledLocalContainer] 2. Shutdown the earlier cacheManager before creating new one with same name.
      [INFO] [talledLocalContainer] The source of the existing CacheManager is: DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ]
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1422)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:518)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:567)
      [INFO] [talledLocalContainer] at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
      [INFO] [talledLocalContainer] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
      [INFO] [talledLocalContainer] at org.hippoecm.hst.site.container.SpringComponentManager.initialize(SpringComponentManager.java:96)
      [INFO] [talledLocalContainer] at org.hippoecm.hst.site.container.HstSiteConfigServlet.initializeComponentManager(HstSiteConfigServlet.java:349)
      [INFO] [talledLocalContainer] at org.hippoecm.hst.site.container.HstSiteConfigServlet$1.reloadingPerformed(HstSiteConfigServlet.java:250)
      [INFO] [talledLocalContainer] at org.apache.commons.configuration.AbstractFileConfiguration.reload(AbstractFileConfiguration.java:834)
      [INFO] [talledLocalContainer] at org.apache.commons.configuration.AbstractFileConfiguration.reload(AbstractFileConfiguration.java:812)
      [INFO] [talledLocalContainer] at org.apache.commons.configuration.AbstractFileConfiguration.getProperty(AbstractFileConfiguration.java:954)
      [INFO] [talledLocalContainer] at org.apache.commons.configuration.AbstractConfiguration.resolveContainerStore(AbstractConfiguration.java:1178)
      [INFO] [talledLocalContainer] at org.apache.commons.configuration.AbstractConfiguration.getString(AbstractConfiguration.java:1044)
      [INFO] [talledLocalContainer] at org.apache.commons.configuration.AbstractConfiguration.getString(AbstractConfiguration.java:1027)
      [INFO] [talledLocalContainer] at org.hippoecm.hst.site.container.HstSiteConfigServlet$HstSiteConfigurationChangesChecker.run(HstSiteConfigServlet.java:685)
      [INFO] [talledLocalContainer] Caused by: net.sf.ehcache.CacheException: Another unnamed CacheManager already exists in the same VM. Please provide unique names for each CacheManager in the config or do one of following:
      [INFO] [talledLocalContainer] 1. Use one of the CacheManager.create() static factory methods to reuse same CacheManager with same name or create one if necessary
      [INFO] [talledLocalContainer] 2. Shutdown the earlier cacheManager before creating new one with same name.
      [INFO] [talledLocalContainer] The source of the existing CacheManager is: DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ]
      [INFO] [talledLocalContainer] at net.sf.ehcache.CacheManager.assertNoCacheManagerExistsWithSameName(CacheManager.java:521)
      [INFO] [talledLocalContainer] at net.sf.ehcache.CacheManager.init(CacheManager.java:371)
      [INFO] [talledLocalContainer] at net.sf.ehcache.CacheManager.<init>(CacheManager.java:356)
      [INFO] [talledLocalContainer] at org.springframework.cache.ehcache.EhCacheManagerFactoryBean.afterPropertiesSet(EhCacheManagerFactoryBean.java:111)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1479)
      [INFO] [talledLocalContainer] at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1419)
      [INFO] [talledLocalContainer] ... 19 more
      [INFO] [talledLocalContainer] 02.11.2012 09:29:27 WARN [org.hippoecm.hst.site.container.HstSiteConfigServlet.initializeComponentManager():378] Exception occurred during stopping componentManager. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ehCacheManager' defined in class path resource [org/hippoecm/hst/site/container/SpringComponentManager-cache.xml]: Invocation of init method failed; nested exception is net.sf.ehcache.CacheException: Another unnamed CacheManager already exists in the same VM. Please provide unique names for each CacheManager in the config or do one of following:
      [INFO] [talledLocalContainer] 1. Use one of the CacheManager.create() static factory methods to reuse same CacheManager with same name or create one if necessary
      [INFO] [talledLocalContainer] 2. Shutdown the earlier cacheManager before creating new one with same name.
      [INFO] [talledLocalContainer] The source of the existing CacheManager is: DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ]
      [INFO] [talledLocalContainer] 02.11.2012 09:29:27 WARN [org.hippoecm.hst.site.container.HstSiteConfigServlet$1.reloadingPerformed():251] HstSiteConfigServlet has completed reinitializing component manager on configuration change.

      Attachments

        Issue Links

          Activity

            People

              aschrijvers Ard Schrijvers
              mdenburger Mathijs den Burger (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: