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

Resolve jersey/jetty startup warnings

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.0.0
    • 3.0.0
    • backend
    • None

      We currently see the following warn log during startup

      1:38:45.503 [main] WARN  org.glassfish.jersey.internal.Errors - The following warnings have been detected: WARNING: Return type, java.util.List<? extends org.camunda.optimize.dto.optimize.DefinitionOptimizeDto>, of method, public java.util.List<? extends org.camunda.optimize.dto.optimize.DefinitionOptimizeDto> org.camunda.optimize.rest.DefinitionRestService.getDefinitions(javax.ws.rs.container.ContainerRequestContext,org.camunda.optimize.dto.optimize.DefinitionType,boolean), is not resolvable to a concrete type.
WARNING: The (sub)resource method getDefinitions in org.camunda.optimize.rest.DefinitionRestService contains empty path annotation.

      15:47:49.189 [main] WARN  o.e.j.s.handler.gzip.GzipHandler - minGzipSize of 0 is inefficient for short content, break even is size 23

      We should resolve the cause to avoid confusion by customers.

        This is the controller panel for Smart Panels app

            [OPT-3495] Resolve jersey/jetty startup warnings

            Johannes added a comment -

            sebastian.bathke: fyi the log output contains also this warning

            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]

            and this warning:

            15:47:49.189 [main] WARN  o.e.j.s.handler.gzip.GzipHandler - minGzipSize of 0 is inefficient for short content, break even is size 23

            Johannes added a comment - sebastian.bathke : fyi the log output contains also this warning 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] and this warning: 15:47:49.189 [main] WARN o.e.j.s.handler.gzip.GzipHandler - minGzipSize of 0 is inefficient for short content, break even is size 23

            Johannes added a comment -

            Let me know if I should help you to resolve one of those

            Johannes added a comment - Let me know if I should help you to resolve one of those

            Sebastian Bathke added a comment - - edited

            johannes.heinemann I would extract the logback warning you referred to to OPT-3500 and keepo the scope of this on jersey/jetty stuff, so including the gzip warning you added

            Sebastian Bathke added a comment - - edited johannes.heinemann I would extract the logback warning you referred to to OPT-3500 and keepo the scope of this on jersey/jetty stuff, so including the gzip warning you added

            Johannes added a comment -

            Sounds good

            Johannes added a comment - Sounds good

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: