[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph closed MAGNOLIA-2911.
------------------------------------
Resolution: Not an issue
Hi,
Without more details about your setup (jdbc url for instance), it's not
possible to give any relevant answer; it looks like a connection issue - did
you see the suggestion in the exception message itself?
Besides, both jackrabbit and the mysql driver are open source, so yes, you do
have the sources ;)
This Jira project is used to report bugs and improvements on the current
codebase.
For such questions or issues, please use either the [mailing
lists|http://documentation.magnolia-cms.com/stay-updated.html#Mailinglists] or
your dedicated [support
channel|http://documentation.magnolia-cms.com/support.html] if you have a
support contract with us. If so, you can directly *Move* this issue under the
*Support - Magnolia* project. The reason we can't do it ourselves is so to
avoid having to guess details about your setup. Your attention to detail will
be appreciated.
If this ends up being an actual bug in Magnolia (or something that can be
improved), we'll be happy to reopen this issue (or create a new one) with the
relevant details to fix it !
Cheers,
-greg
> Insufficient error messages by storage backend classes
> ------------------------------------------------------
>
> Key: MAGNOLIA-2911
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2911
> Project: Magnolia
> Issue Type: Bug
> Components: activation
> Affects Versions: 3.6.5
> Reporter: Thomas Sperger
> Assignee: Philipp Bärfuss
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
