[MAGNOLIA-782] activation with more than approximately 30 pages and 512MB RAM causes out of memory error Created: 22/Mar/06 Updated: 23/Jan/13 Resolved: 08/May/06 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 2.1.5, 3.0 Beta 1 |
| Fix Version/s: | 3.0 Beta 1 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Tom Wespi | Assignee: | Sameer Charles |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
2.1.5, 2 instances |
||
| 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 |
|
a java.lang out of memory error while activation destroys a repository or a branch of the repository, irreparably. Solution: do a better simpleExchange Workaround: 'Activate with Subpages' just allows activation of the site and the children, but not the children of the children. |
| Comments |
| Comment by Sameer Charles [ 08/May/06 ] |
|
re-open this bus with proper log file extracts! I could not reproduce this behaviour with max 512mb assigned to tomcat running 2 instances of magnolia. |