[
https://issues.apache.org/jira/browse/FILEUPLOAD-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206652#comment-14206652
]
Thomas Neidhart commented on FILEUPLOAD-256:
--------------------------------------------
I can not reproduce this problem.
The FileCleaningTracker should be setup by the same context listener once the
context has been initialized. If the respective attribute is null afterwards,
somebody must have reset it to null. A possible explanation would be that your
container has serialized the ServletContext (there are reports on the web about
Weblogic doing this kind of thing). As the FileCleaningTracker is not
serializable, it would not survive such a save/restore process.
Can you give more details about your system configuration?
> FileCleanerCleanup throws NPE on shut-down
> ------------------------------------------
>
> Key: FILEUPLOAD-256
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-256
> Project: Commons FileUpload
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Til Schneider
> Priority: Minor
>
> FileCleanerCleanup throws NPE on shut-down if there was no file uploaded.
> Here's the stack trace:
> {code}
> java.lang.NullPointerException
> at
> org.apache.commons.fileupload.servlet.FileCleanerCleanup.contextDestroyed(FileCleanerCleanup.java:87)
> at
> org.mortbay.jetty.handler.ContextHandler.doStop(ContextHandler.java:600)
> ...
> {code}
> A simple check, whether there is a FileCleaningTracker for that
> ServletContext should fix this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
