Turning on logging & profiling causes a server error, causing further errors in the entire instance

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 5.0.1
    • Affects Version/s: None
    • Component/s: None

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      1. As sysadmin, go to Administration -> Logging & Profiling
      2. Enable Profiling

      Receive error:

      
      java.lang.IllegalStateException: We really expect the implementation of OpTimerFactory to in fact be a ThreadLocalOpTimerFactory
      	at com.atlassian.jira.instrumentation.Instrumentation.snapshotThreadLocalOperationsAndClear(Instrumentation.java:134)
      	at com.atlassian.jira.web.filters.steps.instrumentation.InstrumentationStep.finallyAfterDoFilter(InstrumentationStep.java:46)
      	at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:85)
      	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
      	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
      	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:554)
      	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
      	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
      	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
      	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
      	at java.lang.Thread.run(Thread.java:662)
      

      after this, the same error is seen when accessing the JIRA home page (dashboard).

      To bring the instance back to a workable state, hit

      /secure/admin/ViewLogging!disableProfiling.jspa
      

              Assignee:
              Unassigned
              Reporter:
              Jonathon Creenaune
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: