[MAGNOLIA-904] Starting/stopping Magnolia instance ends in 'Out of Memory' Created: 01/Jun/06 Updated: 23/Jan/13 Resolved: 18/Oct/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Giancarlo Berner | Assignee: | Sameer Charles |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian Linux, Magnolia 2.1.5, Tomcat 5.0 |
||
| 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 read about memory problems with Derby or DB Berkely PM, but am not sure of which. Could that perhaps be something like a 'hint'? |
| Comments |
| Comment by Philipp Bracher [ 01/Jun/06 ] |
|
Fabrizio invested a lot on reduceing the memory usage for 2.1.6 (not yet released 2.1 branch). Can you test the behavior with a 2.1.6-SNAPSHOT? I think It would be cool to release a 2.1.6 (the most robust magnolia ever |
| Comment by Sameer Charles [ 18/Oct/06 ] |
|
Its because (1) You are using derby for production use and its embedded within webapp
|