[MAGNOLIA-2342] OutOfMemory errors Created: 28/Aug/08 Updated: 20/Jan/09 Resolved: 02/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.6.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Jon Larson | Assignee: | Boris Kraft |
| Resolution: | Workaround exists | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Java JDK 1.5 |
||
| 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 |
|
Upgrade from 3.0.3 to 3.5.8 We moved to berkley db JDK Java Options |
| Comments |
| Comment by Jan Haderka [ 28/Aug/08 ] |
|
Hi Jon,
|
| Comment by Jan Haderka [ 02/Sep/08 ] |
|
BDB and Derby are inherently sensitive to memory and usage of memory grows with the size of the database. Switch to backing store that is not running in same JVM (e.g. MySQL) as your Magnolia instance to prevent this kind of problems. |