#384 ✓worksforme
Ivan San José García

Limit size of file upload fails

Reported by Ivan San José García | November 4th, 2010 @ 01:56 PM

When in application.conf set play.netty.maxContentLength to any value,
and upload a file that it size is over that value, this exception was
raised:

play.data.parsing.ApacheMultipartParser$IOFileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly
       at play.data.parsing.ApacheMultipartParser.parse(ApacheMultipartParser.java:565)
       at play.mvc.Scope$Params.checkAndParse(Scope.java:303)
       at play.mvc.Scope$Params.all(Scope.java:370)
       at play.mvc.ActionInvoker.getActionMethodArgs(ActionInvoker.java:470)
       at play.data.validation.ValidationPlugin$Validator.validateAction(ValidationPlugin.java:97)
       at play.data.validation.ValidationPlugin.beforeActionInvocation(ValidationPlugin.java:51)
       at play.mvc.ActionInvoker.invoke(ActionInvoker.java:110)
       at play.server.PlayHandler$NettyInvocation.execute(PlayHandler.java:169)
       at play.Invoker$Invocation.run(Invoker.java:187)
       at play.server.PlayHandler$NettyInvocation.run(PlayHandler.java:149)
       at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
       at java.util.concurrent.FutureTask.run(FutureTask.java:166)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
       at java.lang.Thread.run(Thread.java:636)
Caused by: play.data.parsing.MultipartStream$MalformedStreamException:
Stream ended unexpectedly
       at play.data.parsing.MultipartStream$ItemInputStream.makeAvailable(MultipartStream.java:902)

       at play.data.parsing.MultipartStream$ItemInputStream.read(MultipartStream.java:825)
       at java.io.InputStream.read(InputStream.java:102)
       at org.apache.commons.fileupload.util.Streams.copy(Streams.java:94)
       at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64)
       at play.data.parsing.ApacheMultipartParser.parse(ApacheMultipartParser.java:561)
       ... 17 more
16:27:31,761 ERROR ~

@64c7a57im
Internal Server Error (500) for request POST /uploadCaptura

Oops: IllegalStateException
An unexpected error occured caused by exception IllegalStateException:
Error when handling upload

play.exceptions.UnexpectedException: Unexpected Error
       at play.data.validation.ValidationPlugin.beforeActionInvocation(ValidationPlugin.java:59)
       at play.mvc.ActionInvoker.invoke(ActionInvoker.java:110)
       at Invocation.HTTP Request(Play!)
Caused by: java.lang.IllegalStateException: Error when handling upload
       at play.data.parsing.ApacheMultipartParser.parse(ApacheMultipartParser.java:592)
       at play.mvc.Scope$Params.checkAndParse(Scope.java:303)
       at play.mvc.Scope$Params.all(Scope.java:370)

       at play.mvc.ActionInvoker.getActionMethodArgs(ActionInvoker.java:470)
       at play.data.validation.ValidationPlugin$Validator.validateAction(ValidationPlugin.java:97)
       at play.data.validation.ValidationPlugin.beforeActionInvocation(ValidationPlugin.java:51)
       ... 2 more
Caused by: play.data.parsing.ApacheMultipartParser$IOFileUploadException:
Processing of multipart/form-data request failed. Stream ended
unexpectedly
       at play.data.parsing.ApacheMultipartParser.parse(ApacheMultipartParser.java:565)
       ... 7 more
Caused by: play.data.parsing.MultipartStream$MalformedStreamException:
Stream ended unexpectedly
       at play.data.parsing.MultipartStream$ItemInputStream.makeAvailable(MultipartStream.java:902)
       at play.data.parsing.MultipartStream$ItemInputStream.read(MultipartStream.java:825)
       at java.io.InputStream.read(InputStream.java:102)
       at org.apache.commons.fileupload.util.Streams.copy(Streams.java:94)
       at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64)
       at play.data.parsing.ApacheMultipartParser.parse(ApacheMultipartParser.java:561)
       ... 7 more

I thinked that this bug was fixed as appears on
https://bugs.launchpad.net/play/+bug/621029 . But seems to be unfixed.

Version: Play! 1.1

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Pages