[MAGNOLIA-2911] Insufficient error messages by storage backend classes Created: 27/Oct/09 Updated: 28/Oct/09 Resolved: 28/Oct/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Thomas Sperger | Assignee: | Philipp Bärfuss |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| 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... activated 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 |
| Comments |
| Comment by Magnolia International [ 28/Oct/09 ] |
|
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? 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 or your dedicated support channel 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 |