Hibernate missing cache generates warning level log messages on start-up

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 8.1.1
    • Affects Version/s: 7.0.0, 7.1.0, 7.0.2, 7.0.1, 7.0.3, 7.0.4, 7.0.6, 7.2.0, 7.1.2, 7.1.1, 7.1.3, 7.1.4, 7.2.1, 7.2.2
    • Component/s: Logs
    • 1
    • Severity 3 - Minor

      Issue Summary

      Incorrect warning messages causes warning level log messages to be logged upon start-up.

      Steps to Reproduce

      1. Start Bamboo

      Expected Results

      No warning messages.

      Actual Results

      The warning messages are shown in the atlassian-bamboo.log file:

      WARN [performSetupDatabaseConnectionBackgroundThread] [cache] HHH90001006: Missing cache[default-update-timestamps-region] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
      WARN [performSetupDatabaseConnectionBackgroundThread] [cache] HHH90001006: Missing cache[default-query-results-region] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
      WARN [performSetupDatabaseConnectionBackgroundThread] [cache] HHH90001006: Missing cache[bucket.user.propertyset.BucketPropertySetItem] was created on-the-fly. The created cache will use a provider-specific default configuration: make sure you defined one. You can disable this warning by setting 'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
      

      Workaround

      Currently there's no workaround.

            Assignee:
            Marcin Gardias
            Reporter:
            Karel Miranda
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: