[MAGNOLIA-2160] Getting ItemNotFoundException followed by OutOfMemoryError all the time Created: 29/May/08 Updated: 17/Mar/09 Resolved: 29/May/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Rüdiger Engelberger | Assignee: | Philipp Bärfuss |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows XP, Apache Tomcat 5.5.25 |
||
| Attachments: |
|
| 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 |
|
I've downloaded and installed Magnolia Community Edition bundled with Tomcat (magnolia-tomcat-bundle-3.5.4-bundle-jdk15.zip) and using it since some days. But I'm always getting the same exception: javax.jcr.ItemNotFoundException: 75a3f541-568d-49e2-bfbe-eac355425777 -> see full stack trace attached -> this exception is always followed by a OutOfMemoryError And this error happens in a lot of different situations ... when editing / copying a dialog / template definition in the Configuration section or when editing a dialog to fill the contents of a page in Website section etc. Is there a severe bug in this version? This error happens very often (all 3-10 min of work). After that I have to restart Tomcat. So at the moment I can't use Magnolia for production use. Does anybody have an idea? Thanks a lot! Rüdiger Engelberger |
| Comments |
| Comment by Philipp Bracher [ 29/May/08 ] |
|
You have to assign tomcat (magnolia) enough memory. The easiest way to do that is using the magnolia.sh or magnolia.bat script which does it for you. Please note that we are releasing 3.5.8 which contains some additional memory related fixes. In general we advise to use a external database like mysql in production |