Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71739

Attempting to Roll logs causes "Null pointer exception" if using WARN logging level with "com.atlassian.jira.util.log.LogMarker" package

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 8.4.2, 8.5.5, 8.13.0
    • Environment - Java

    Description

      Issue Summary

      Attempting to Roll logs causes "Null pointer exception" if using WARN logging level with "com.atlassian.jira.util.log.LogMarker" package.

      Steps to Reproduce

      1. Edit log4jproperties ($JIRA_INSTALL/atlassian-jira/WEB-INF/classes) and modify the following package to use WARN debug level:
        log4j.logger.com.atlassian.jira.util.log.LogMarker = WARN, console, filelog, httpaccesslog, httpdumplog, sqllog, querydsllog, slowquerylog, slowsqlquerylog, xsrflog, securitylog, outgoingmaillog, incomingmaillog, remoteappssecurity, apdexlog
        
      2. Restart Jira
      3. Go to Logging and profiling page
      4. Click "Log Rollover", enter "Optional Message" and click "Mark

      Expected Results

      Logs get rolled over, but nothing is displayed as a mark message, since the WARN level was applied to the logger.

      Actual Results

      The following page gets displayed in the browser window:

      The below exception is thrown in the xxxxxxx.log file:

      2020-09-19 13:01:23,627+0300 https-jsse-nio-8443-exec-170 ERROR      [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=246beb71-94d7-437a-87a2-c13d5b66f2be, interpretedMsg=, cause=java.lang.NullPointerException, stacktrace=java.lang.NullPointerException
          	at java.io.File.<init>(File.java:277) [?:1.8.0_242]
          	at com.atlassian.jira.util.log.LogMarker.rolloverAsAppropropriate(LogMarker.java:76) [classes/:?]
          	at com.atlassian.jira.util.log.LogMarker.rollover(LogMarker.java:70) [classes/:?]
          	at com.atlassian.jira.util.log.LogMarker.rolloverAndMark(LogMarker.java:53) [classes/:?]
          	at com.atlassian.jira.cluster.logging.ClusterLoggingManager.mark(ClusterLoggingManager.java:89) [classes/:?]
          	at com.atlassian.jira.cluster.logging.ClusterLoggingManager.markLogs(ClusterLoggingManager.java:68) [classes/:?]
          	at com.atlassian.jira.web.action.admin.ViewLogging.doMarkLogs(ViewLogging.java:135) [classes/:?]
          	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.8.0_242]
          	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [?:1.8.0_242]
          	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.8.0_242]
          	at java.lang.reflect.Method.invoke(Method.java:498) [?:1.8.0_242]
          	at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:438) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.action.ActionSupport.execute(ActionSupport.java:157) [webwork-1.4-atlassian-30.jar:?]
          	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-8.5.4.jar:?]
          	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) [webwork-1.4-atlassian-30.jar:?]
          	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) [webwork-1.4-atlassian-30.jar:?]
          	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:138) [classes/:?]
          	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) [servlet-api.jar:?]
          	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [catalina.jar:8.5.42]
          	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.42]
          	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat-websocket.jar:8.5.42]
          	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:8.5.42]
          	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.42]
          	at com.atlassian.jira.web.filters.JiraLastFilter.lambda$doFilter$0(JiraLastFilter.java:39) [classes/:?]
          	at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:74) [classes/:?]
          	at com.atlassian.jira.web.filters.JiraLastFilter.doFilter(JiraLastFilter.java:36) [classes/:?]
          	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:8.5.42]
      ...
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mfilipan Marko Filipan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: