[
https://issues.apache.org/jira/browse/MYFACES-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827661#comment-13827661
]
Sebastian Leske commented on MYFACES-3736:
------------------------------------------
Looking at the source code, the problem is that _any_ IOException that occurs
while reading the resource data and sending it over the network will trigger
this message.
However, such an IOException can indicate many different problems, some
serious, some not.
In particular, if the loading of the resource fails, there is typically a
serious problem on the server (such as a damaged JAR file, or a filesystem
error). If the sending fails, it is probably because of a network problem (like
in this case), which is not an error, at least not for the server.
Ideally, the code should somehow distinguish these problems, for example by
specifically checking for exceptions that indicate a network problem. I
attached a patch which does that for the ClientAbortException from Tomcat.
However, this check will only work for Tomcat - I could not find a general way
to check.
If using container-specific checks is not acceptable, I believe the severity
should be downgraded from SEVERE to WARNING. The exception may or may not
indicate a real problem, so WARNING seems most appropriate, as it is (to cite
the Javadocs) "a message level indicating a potential problem".
> Occasional ResourceHandlerImpl Error trying to load resource jsf.js with
> library javax.faces
> --------------------------------------------------------------------------------------------
>
> Key: MYFACES-3736
> URL: https://issues.apache.org/jira/browse/MYFACES-3736
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.1.10
> Environment: Windows Server 2008 R2
> Java 1.7.0_07
> Apache Tomcat 7.0.39
> Reporter: Moshe Elisha
>
> From time to time I encountered the following error:
> ERROR http-apr-80-exec-2 ResourceHandlerImpl:425: Error trying to load
> resource jsf.js with library javax.faces :null
> That is all I have. I can't tell what the exact request details or what is
> the IOException.
> Can you please also make it possible to log the IOException stacktrace?
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
