[MAGNOLIA-2335] Apache mod_proxy configuration Created: 20/Aug/08 Updated: 20/Jan/09 Resolved: 20/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.5.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jon Larson | Assignee: | Boris Kraft |
| Resolution: | Inactive | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Hardware = HP DL380G4 (CPU=Dual Xeon 3Ghz, MEM=2G, Raid 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 |
|
We are in the process of migrating from magnolia 3.0.2 + derby to magnolia 3.5.8 + berkley. I ran into a couple snags after the upgrade with apache 2 serving the pages via a reverse proxy. The first problem was that with the original configuration below the index page for the site was not displayed so I refactored the mod_proxy configuration"below" to fix the problem. After 12 hours online it threw a java heap OutofMemory error. Catalina.sh Old Config New Config
|
| Comments |
| Comment by Magnolia International [ 20/Aug/08 ] |
|
Jon, you probably wanted to report this as a support request? You already have a userid which has the appropriate permissions (jlarson), and you've already used the system (SUPPORT-9). Could you please recreate your issues there, so that we have all the appropriate information filled in correctly ? Thanks. |
| Comment by Magnolia International [ 20/Jan/09 ] |
|
Memory issues usually won't happen unless you have extravagant documents or extraordinary usages. We'd need to make sure your setup is correct, which is hard to say here (we'd need more info, log files, etc). The issue is most probably not related to mod_proxy. |