On Mon, Apr 29, 2013 at 11:52 PM, Thomas Misilo <[email protected]> wrote: > Already looked at this thread. And just compared against the > build.properties and the dspace.cfg file and they match as they should.
OK, so both your org.apache.cocoon.uploads.maxsize and upload.max are set to 2147483647 (2 GB). Are you sure that's the case in the version you have deployed, not just the source? It should be 2 GB and 512 MB, respectively, if you used the default 3.1 configuration. Do you use Apache HTTPD in front of Tomcat? If you do, do you have the LimitRequestBody directive set in your HTTPD configuration? I do not think HTTPD is the problem, but it doesn't hurt to check. This is due to Cocoon checking its configuration for limitation and explicitly throwing an exception: http://grepcode.com/file/repo1.maven.org/maven2/org.apache.cocoon/cocoon-core/2.2.0-M1/org/apache/cocoon/servlet/multipart/RejectedPart.java#80 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
