Uploaded image for project: '[Read Only] - CRISP'
  1. [Read Only] - CRISP
  2. CRISP-21

RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 2.1.0
    • None

    Description

      RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup.
      Since /site webapp can be initialized before /cms (having RepositoryServlet), the repository can be unavailable for a while.
      Therefore, it doesn't have to print full stack traces on initialization in that specific case.

      Attachments

        Issue Links

          is backported by

          Improvement - An improvement or enhancement to an existing feature or task. CRISP-22 [Backport for v12.0] RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. CRISP-25 [Backport for v11] RepositoryMapResourceResolverProvider#ResourceResolversInitializingThread prints stack traces unnecessarily on startup

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Activity

            People

              wko Woonsan Ko (Inactive)
              wko Woonsan Ko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: