Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-6080

Intermittent issues with CMS UI in our release environment

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Top
    • Resolution: Fixed
    • 2.22.02
    • None
    • None

    Description

      We have seen multiple problems in our Release environment in the past 24 hours. Twice the UI has become unresponsive. The logs show the same pattern each time. Attached is the log file. Some examples are listed below.

      Preliminary health checks indicate that the servers are not under serious load at the time of the issues. We are continuing to investigate on our side, but please take a look at our logs and let us know if you need any more information.

      Thanks.

      17.04.2012 06:39:10 ERROR [org.apache.wicket.RequestCycle.logRuntimeException():1531] org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is still locked by: Thread[http-8080-7,5,main], giving up trying to get the page for path: 1:root:pinger
      org.apache.wicket.protocol.http.request.InvalidUrlException: org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is still locked by: Thread[http-8080-7,5,main], giving up trying to get the page for path: 1:root:pinger
      at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:262)
      at org.apache.wicket.RequestCycle.step(RequestCycle.java:1312)
      ...
      Caused by: org.apache.wicket.WicketRuntimeException: After 1 minute the Pagemap null is still locked by: Thread[http-8080-7,5,main], giving up trying to get the page for path: 1:root:pinger
      at java.util.HashMap.<init>(Unknown Source)
      at java.util.HashSet.<init>(Unknown Source)
      at org.hippoecm.frontend.plugin.impl.ServiceForwarder.onServiceAdded(ServiceForwarder.java:92)

      -------------

      17.04.2012 06:54:40 ERROR [org.apache.jackrabbit.core.util.db.ConnectionHelper$RetryManager.doTry():498] Failed to execute SQL (stacktrace on DEBUG log level)
      com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

      The last packet successfully received from the server was 16,626 milliseconds ago. The last packet sent successfully to the server was 92 milliseconds ago.
      ...
      Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
      at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:2540)
      at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2990)

      Attachments

        Activity

          People

            mbrand Mathijs Brand (Inactive)
            pminutillo Peter Minutillo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: