You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Haroldo de Oliveira Pinheiro (Created) (JIRA)" <de...@myfaces.apache.org> on 2012/04/05 15:09:23 UTC

[jira] [Created] (MYFACES-3524) MyFaces returns a blank page whenever there's some error. Nothing on the log, either.

MyFaces returns a blank page whenever there's some error. Nothing on the log, either.
-------------------------------------------------------------------------------------

                 Key: MYFACES-3524
                 URL: https://issues.apache.org/jira/browse/MYFACES-3524
             Project: MyFaces Core
          Issue Type: Improvement
    Affects Versions: 2.1.6
         Environment: JDK 1.6.0_31
Tomcat 7.0.26
tomahawk20-1.1.11 
            Reporter: Haroldo de Oliveira Pinheiro


We were migrating from MyFaces 1.1.8 to MyFaces 2.1.6, when we ran into a really crippling problem:
Whenever an uncaught error happens, MyFaces 2.1.6 just returns a blank page, and doesn't show anything on the log, either. Naturally, this error makes it almost impossible to even find out what error is ocurring. 
Couldn't the error at least be shown in the log?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (MYFACES-3524) MyFaces returns a blank page whenever there's some error. Nothing on the log, either.

Posted by "Leonardo Uribe (Commented) (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/MYFACES-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253032#comment-13253032 ] 

Leonardo Uribe commented on MYFACES-3524:
-----------------------------------------

Probably there is an error in render response phase. The response was already started and cannot be reset, so the default error handler cannot reset the response and render the error page. 

You should attach a debugger into your tomcat to see what's wrong. I don't think the solution is in MyFaces in this case.
                
> MyFaces returns a blank page whenever there's some error. Nothing on the log, either.
> -------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3524
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3524
>             Project: MyFaces Core
>          Issue Type: Improvement
>    Affects Versions: 2.1.6
>         Environment: JDK 1.6.0_31
> Tomcat 7.0.26
> tomahawk20-1.1.11 
>            Reporter: Haroldo de Oliveira Pinheiro
>
> We were migrating from MyFaces 1.1.8 to MyFaces 2.1.6, when we ran into a really crippling problem:
> Whenever an uncaught error happens, MyFaces 2.1.6 just returns a blank page, and doesn't show anything on the log, either. Naturally, this error makes it almost impossible to even find out what error is ocurring. 
> Couldn't the error at least be shown in the log?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira