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

NullPointerException when Switching between Projects or Boards

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Medium
    • None
    • 4.1.2
    • None
    • atlassian-jira-enterprise-4.1.2.zip, jdk 1.6.0.16, Suse Linux 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux

    Description

      In my case, the WEB-INF/classes/log4j.properties included has these loggers turned off, but they still seem to run. I am including a patch that ignores the NullPointerException following the pattern of ignoring the ClassNotFoundException.

      Details below taken from: http://confluence.atlassian.com/display/GHKB/NullPointerException+when+Switching+between+Projects+or+Boards

      Symptoms
      When switching between projects or boards using the "Agile" menu, an error like the following appears onscreen and in the logs:
      java.lang.NullPointerException
      at com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor$CallStack.isProtectedAction(XsrfVulnerabilityDetectionSQLInterceptor.java:161)
      at com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor.afterExecutionImpl(XsrfVulnerabilityDetectionSQLInterceptor.java:75)
      at com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor.afterSuccessfulExecution(XsrfVulnerabilityDetectionSQLInterceptor.java:40)
      at com.atlassian.jira.ofbiz.ChainedSQLInterceptor.afterSuccessfulExecution(ChainedSQLInterceptor.java:70)
      at org.ofbiz.core.entity.jdbc.SQLProcessor.afterExecution(SQLProcessor.java:552)

      Cause
      There is a known problem with JIRA and a particular logger that manifests itself when logging for the XsrfVulnerabilityDetectionSQLInterceptor is enabled. This problem manifests itself when switching from project to project or board to board using the "Agile" menu.

      Resolution
      By default, the logger that causes this problem is disabled. If you're experiencing this problem, please check your log4j.properties file and any additional log configuration files. Your log4j.properties file should contain lines like the following:

      log4j.logger.com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor = OFF
      , xsrflog
      log4j.additivity.com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor =
      false

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              83df7e9830a8 Brooke Hedrick
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0.25h
                  0.25h
                  Remaining:
                  Remaining Estimate - 0.25h
                  0.25h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified