[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22562#action_22562
]
Jan Haderka commented on MAGNOLIA-2711:
---------------------------------------
Can't think of any other explanation. Probably related to the {{AsyncAppender}}
we use. See {{WEB-INF/config/default/log4j.xml}}
{code}
<appender name="log-debug" class="org.apache.log4j.AsyncAppender">
{code}
There is also similar issue with log4j 1.1 (closed as won't fix, because of
being outdated)
https://issues.apache.org/bugzilla/show_bug.cgi?id=14926
> Failure to resolve class when finishing installation leads to 404 page being
> displayed after installation
> ---------------------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2711
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2711
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Jan Haderka
> Assignee: Boris Kraft
> Attachments: stacktrace.txt
>
>
> Stacktrace attached. Hitting the back button and clicking on "Start Magnolia"
> button again leads to admin interface being displayed (on author) as
> expected. The exception in UI appears most likely because initialization is
> not finished yet. We should either postpone those or make sure some better
> page is displayed then default tomcat's 404.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
