I've also posted about the issue on Stack Overflow here: http://stackoverflow.com/questions/3177092/uploading-to-blobstore-gives-a-java-heap-outofmemoryerror
Hopefully getting some more eyeballs on it will help. On Jul 4, 10:47 pm, Adrian Petrescu <apetr...@gmail.com> wrote: > I'm having the exact same issue too, down to the line numbers in the > stack trace. > > Has anyone figured out what is causing this? I find it hard to believe > we've all made the exact same identical mistake, all within the last > month. Is something wrong on Google's end? > > Cheers, > Adrian > > On Jun 2, 7:14 pm, Jean Hsu <jeanhs...@gmail.com> wrote: > > > > > Hi all, > > > I am trying to set up a basic file upload to blobstore, but I get > > this OutOfMemoryError: > > > WARNING: Error for /_ah/upload/ > > aghvbWdkcmVzc3IcCxIVX19CbG9iVXBsb2FkU2Vzc2lvbl9fGMACDA > > java.lang.OutOfMemoryError: Java heap space > > at java.util.Arrays.copyOf(Arrays.java:2786) > > at > > java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:71) > > at > > javax.mail.internet.MimeMultipart.readTillFirstBoundary(MimeMultipart.java: > > 316) > > at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:186) > > at > > javax.mail.internet.MimeMultipart.getCount(MimeMultipart.java:109) > > at > > com.google.appengine.api.blobstore.dev.UploadBlobServlet.handleUpload(Uploa > > dBlobServlet.java: > > 135) > > at com.google.appengine.api.blobstore.dev.UploadBlobServlet.access > > $000(UploadBlobServlet.java:72) > > at com.google.appengine.api.blobstore.dev.UploadBlobServlet > > $1.run(UploadBlobServlet.java:100) > > at java.security.AccessController.doPrivileged(Native Method) > > at > > com.google.appengine.api.blobstore.dev.UploadBlobServlet.doPost(UploadBlobS > > ervlet.java: > > 98) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > > at > > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: > > 511); > > > I used the Memory Analyzer on Eclipse and it said that the memory leak > > suspect is QueuedThreadPool. I found this information about a memory > > leak bug: > > >http://jira.codehaus.org/browse/JETTY-1188 > > > How can I figure out what release of jetty is running locally? It > > looks like they fixed this in version 6.1.23: > > >http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11160&vers... > > > Has anyone else had this issue? > > > Thanks, > > Jean -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
