We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3500

Optimize Upgrade and distribution start throws warnings

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.0.0
    • 3.0.0
    • backend
    • None

      Upgrade case:

      • given:
        • I run and use Optimize 2.7.0
      • when:
        • I run the upgrade script of Optimize 3.0.0
      • then:
        • I see the following warnings:
          [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/optimize-backend-3.0.0.jar!/logback.xml]
          14:48:44,050 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml]
          14:48:44,064 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@3a93b025 - URL [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml] is not of type file
          
      • expected:
        • there are no warnings in the log

      Running Optimize case:

      • given:
        • I upgraded to Optimize 3.0.0
      • when:
        • I run Optimize 3.0.0
      • then:
        • I see the following warnings:
          15:47:48,448 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
          15:47:48,449 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
          15:47:48,449 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml]
          15:47:48,450 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
          15:47:48,450 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/optimize-backend-3.0.0.jar!/logback.xml]
          15:47:48,450 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml]
          
      • expected:
        • there are no warnings in the log

        This is the controller panel for Smart Panels app

            Loading...
            Uploaded image for project: 'Camunda Optimize'
            1. Camunda Optimize
            2. OPT-3500

            Optimize Upgrade and distribution start throws warnings

              • Icon: Bug Report Bug Report
              • Resolution: Fixed
              • Icon: L3 - Default L3 - Default
              • 3.0.0
              • 3.0.0
              • backend
              • None

                Upgrade case:

                • given:
                  • I run and use Optimize 2.7.0
                • when:
                  • I run the upgrade script of Optimize 3.0.0
                • then:
                  • I see the following warnings:
                    [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/optimize-backend-3.0.0.jar!/logback.xml]
                    14:48:44,050 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml]
                    14:48:44,064 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@3a93b025 - URL [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml] is not of type file
                    
                • expected:
                  • there are no warnings in the log

                Running Optimize case:

                • given:
                  • I upgraded to Optimize 3.0.0
                • when:
                  • I run Optimize 3.0.0
                • then:
                  • I see the following warnings:
                    15:47:48,448 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
                    15:47:48,449 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
                    15:47:48,449 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml]
                    15:47:48,450 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
                    15:47:48,450 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/optimize-backend-3.0.0.jar!/logback.xml]
                    15:47:48,450 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/home/johannes/Test/Optimize/camunda-optimize-3.0.0-production/lib/optimize-commons-3.0.0.jar!/logback.xml]
                    
                • expected:
                  • there are no warnings in the log

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        johannes.heinemann Johannes
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        0 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              johannes.heinemann Johannes
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              0 Start watching this issue

                                Created:
                                Updated:
                                Resolved: