Uploaded image for project: 'Hippo Site Toolkit 2'
  1. Hippo Site Toolkit 2
  2. HSTTWO-1736

"Failed to get a session in EventListenerContainer" message should be logged at INFO level

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.22.04, 2.23.02
    • Component/s: None
    • Labels:
      None
    • Similar issues:

      Description

      When starting up the archetype now you will see the following message printed to the console several times until the cms has started up:

      [INFO] [talledLocalContainer] 15.08.2011 11:54:37 WARN [org.hippoecm.hst.core.jcr.EventListenersContainerImpl.doInit():277] Failed to get a session in EventListenersContainer. The repository might be not available yet or the credentials might be wrong. It will try initialization next time. javax.jcr.LoginException: Failed to borrow session from the pool. javax.jcr.RepositoryException: javax.jcr.RepositoryException: No repository found at: vm://

      Somehow the order in which cargo/tomcat deploys the site and the cms has changed. It used to be that the cms was deployed before the site, now it's the other way around. This is what causes these messages to appear.

      Now, the order in which wars are deployed cannot be set in either tomcat or cargo. To get rid of these messages we should set the log level of these messages to INFO.

        Attachments

          Activity

            People

            • Assignee:
              aschrijvers Ard Schrijvers
              Reporter:
              uhommes Unico Hommes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: