java.lang.IllegalStateException: Timer 0 in wrong state to be started. Current state is LOCKED

Oracle Community | 387135 | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Provider error on PortletRendererUtil.renderPortletHeader(...)

    Oracle Community | 1 decade ago | 387135
    java.lang.IllegalStateException: Timer 0 in wrong state to be started. Current state is LOCKED

    Root Cause Analysis

    1. java.lang.IllegalStateException

      Timer 0 in wrong state to be started. Current state is LOCKED

      at oracle.webdb.provider.v2.monitor.InternalPerfMonitor$PerfTimer.start()
    2. oracle.webdb.provider
      InternalPerfMonitor.startTimer
      1. oracle.webdb.provider.v2.monitor.InternalPerfMonitor$PerfTimer.start(Unknown Source)
      2. oracle.webdb.provider.v2.monitor.InternalPerfMonitor.startTimer(Unknown Source)
      2 frames
    3. oracle.portal.provider
      PortletRendererUtil.renderPortletHeader
      1. oracle.portal.provider.v2.render.PortletContainerRenderer.renderPortletHeader(Unknown Source)
      2. oracle.portal.provider.v2.render.PortletRendererUtil.renderPortletHeader(Unknown Source)
      3. oracle.portal.provider.v2.render.PortletRendererUtil.renderPortletHeader(Unknown Source)
      3 frames
    4. org.apache.jsp
      snoop2_jsp._jspService
      1. org.apache.jsp.htdocs.snoop.snoop2_jsp._jspService(snoop2_jsp.java:52)
      1 frame