You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/01/29 22:52:20 UTC
[jira] Updated: (MRM-1024) Archiva throws NPE when a user uploads a
large artifact
[ http://jira.codehaus.org/browse/MRM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1024:
------------------------------
Fix Version/s: 1.x
> Archiva throws NPE when a user uploads a large artifact
> -------------------------------------------------------
>
> Key: MRM-1024
> URL: http://jira.codehaus.org/browse/MRM-1024
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.2-M1
> Reporter: Chris Anders
> Priority: Critical
> Fix For: 1.x
>
> Attachments: NPE-server.txt, NPE-user.txt
>
>
> When a user uploads a file larger then 2097152bytes they are presented with a meaningless NPE (attached as NPE-user.txt) and the server throws a NPE (attached as NPE-server.txt) but also contains the following:
> Nov 27, 2008 2:58:14 AM org.apache.struts2.dispatcher.Dispatcher getSaveDir
> INFO: Unable to find 'struts.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir
> Nov 27, 2008 2:58:14 AM org.apache.struts2.dispatcher.multipart.JakartaMultiPartRequest parse
> SEVERE: org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because its size (2346064) exceeds the configured maximum (2097152)
> Nov 27, 2008 2:58:14 AM org.apache.struts2.interceptor.FileUploadInterceptor intercept
> SEVERE: the request was rejected because its size (2346064) exceeds the configured maximum (2097152)
> Nov 27, 2008 2:58:15 AM org.apache.catalina.core.StandardWrapperValve invoke
> SEVERE: Servlet.service() for servlet default threw exception
> With some digging i found that i could increase this limit by adding "struts.multipart.maxSize=20971520" to webapps/archiva/ROOT/WEB-INF/classes/struts.properties which i have tested
> archiva needs to handle this exception better to the user/server and there needs to be a mechanism to define the max file size in a better solution
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira