Certainly seems correct. Have you double checked that the property
isn't duplicated or wasn't reset by the WAR being unpacked again?
Thanks,
Brett
On 04/09/2009, at 2:51 AM, Robert Munteanu wrote:
As a follow-up, using the web interface leads to
(archiva.log)
2009-09-03 19:32:53,828 [TP-Processor9] ERROR
org.apache.struts2.dispatcher.multipart.MultiPartRequest -
org.apache.commons.fileupload.FileUploadBase
$SizeLimitExceededException: the
request was rejected because its size (19965835) exceeds the
configured
maximum (10485760)
2009-09-03 19:32:53,862 [TP-Processor9] ERROR
org.apache.struts2.interceptor.FileUploadInterceptor - the request
was
rejected because its size (19965835) exceeds the configured maximum
(10485760)
and receiving a connection reset response in the brower.
Strangely enough, I modified the struts.properties file directly in
the war
file to read
struts.multipart.maxSize=31457280
Any ideas as to why this happens?
--
View this message in context:
http://www.nabble.com/Unable-to-deploy-released-war-file-to-archiva-tp25265603p25279947.html
Sent from the archiva-users mailing list archive at Nabble.com.
