[MAGNOLIA-3358] Occasional failure to startup instance due to Log4J initialization errors Created: 03/Nov/10 Updated: 01/Dec/10 Resolved: 01/Dec/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Haderka | Assignee: | Boris Kraft |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Description |
|
As it happens sometimes instance fails to be initialized due to log4j triggered npe in the java.io.Writer. Happens only on standalone instance of tomcat (5.5.27 was the one i used) and occurs only in approx 1 out of 10-20 start ups. |