Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-2911

Insufficient error messages by storage backend classes

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not an issue
    • Major
    • None
    • 3.6.5
    • activation
    • None

    Description

      Our tomcat errorlog shows the following errors/warnings during a activation process. The messages don't tell what's in fact the problem. A simple "failed" is not sufficient. Could you please tell me what happend here. Note: the database (mysql backend) were running all the time.

      WARN org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager DatabasePersistenceManager.java(executeStmt:866) 27.10.2009 07:39:48 execute failed, about to reconnect...
      WARN org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager DatabasePersistenceManager.java(executeStmt:866) 27.10.2009 07:48:12 execute failed, about to reconnect...
      WARN org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager DatabasePersistenceManager.java(executeStmt:866) 27.10.2009 07:48:22 execute failed, about to reconnect...
      WARN org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager DatabasePersistenceManager.java(executeStmt:866) 27.10.2009 07:48:23 execute failed, about to reconnect...
      ERROR org.apache.jackrabbit.core.persistence.db.DatabasePersistenceManager DatabasePersistenceManager.java(store:486) 27.10.2009 07:49:20 failed to write property state: 0a6ce5f8-782b-4b6e-
      a872-b0dae5c0cf5b/

      {http://www.magnolia.info/jcr/mgnl}

      activated
      com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was50031 seconds ago.The last packet sent successfully to the server was 50031 s
      econds ago, which is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increas
      ing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
      at sun.reflect.GeneratedConstructorAccessor52.newInstance(Unknown Source)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
      at com.mysql.jdbc.Util.handleNewInstance(Util.java:406)
      at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1074)
      at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3246)
      at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1917)
      at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060)
      at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2542)
      at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1734)
      at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:995)
      [..]

      Especially the stacktrace is not helpful as I don't have the source.

      Please tell what happend and fix the error messages thrown by storage backends. Thanks

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              izb-isp-team Thomas Sperger
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD