[jira] Commented: (WW-2240) FileUploadInterceptor causes null pointer exception

["Benjamin McCann (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/struts/browse/WW-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42418 ] 

Benjamin McCann commented on WW-2240:
-------------------------------------

That line in the source is a logging call.  Simply add the following around the call:
if(LOG.isInfoEnabled()) {

}

That will solve the problem 90% of the time.  It's not the correct solution, which should still be investigated, but should be added regardless for performance reasons.  Info logs should always be checked in this manner and debug logs checked with isDebugEnabled().

> FileUploadInterceptor causes null pointer exception
> ---------------------------------------------------
>
>                 Key: WW-2240
>                 URL: https://issues.apache.org/struts/browse/WW-2240
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Interceptors
>    Affects Versions: 2.1.0
>            Reporter: Benjamin McCann
>
> Using struts2-core-2.1.0-SNAPSHOT-20071003.jar, I received the following:
> java.lang.NullPointerException
> 	at org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:277)
> 	at com.opensymphony.xwork2.DefaultActionInvocation$1.doProfiling(DefaultActionInvocation.java:229)
> 	at com.opensymphony.xwork2.DefaultActionInvocation$1.doProfiling(DefaultActionInvocation.java:228)
> 	at com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:226)
> My action was able to access the File, so it must have been something in the cleanup.  My action was very similar to the one found in this tutorial http://www.roseindia.net/struts/struts2/struts-2-file-upload.shtml

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.