Here's what I get from live http headers when I deploy and try to upload. It tries to do a get on the uploadUrl, for test.nocache.js, and also later for css. I get a 405 Method Not Allowed for these. Any ideas why it's trying to do a get??
POST /_ah/upload/ AMmfu6ZRpZf67ospmbfJKHd0AKnI9LFkWSDeDuGECy_md0wTVCgPaA9nVuqSg3MUlLJM26dP9I421TDZriqztBSoT7vDEq_Eeel0lhoWwoD1JgFj2pA7bSI/ ALBNUaYAAAAATA2SyHej3Q3PwRuq5WJuE0QxgQPHYGMk/ HTTP/1.1 ... HTTP/1.1 200 OK Server: Upload Server Built on May 19 2010 13:39:25 (1274301565) Etag: "N3jo2g" Date: Tue, 08 Jun 2010 00:36:01 GMT Expires: Fri, 01 Jan 1990 00:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate X-AppEngine-Estimated-CPM-US-Dollars: $0.000052 X-AppEngine-Resource-Usage: ms=2 cpu_ms=0 api_cpu_ms=0 Content-Type: text/html Pragma: no-cache Content-Length: 2590 ---------------------------------------------------------- http://<app-name>.appspot.com/_ah/upload/AMmfu6ZRpZf67ospmbfJKHd0AKnI9LFkWSDeDuGECy_md0wTVCgPaA9nVuqSg3MUlLJM26dP9I421TDZriqztBSoT7vDEq_Eeel0lhoWwoD1JgFj2pA7bSI/ALBNUaYAAAAATA2SyHej3Q3PwRuq5WJuE0QxgQPHYGMk/test/test.nocache.js GET /_ah/upload/ AMmfu6ZRpZf67ospmbfJKHd0AKnI9LFkWSDeDuGECy_md0wTVCgPaA9nVuqSg3MUlLJM26dP9I421TDZriqztBSoT7vDEq_Eeel0lhoWwoD1JgFj2pA7bSI/ ALBNUaYAAAAATA2SyHej3Q3PwRuq5WJuE0QxgQPHYGMk/test/test.nocache.js HTTP/ 1.1 Host: <app-name>.appspot.com User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: 1.9.2.3) Gecko/20100401 Firefox/3.6.3 Accept: */* Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Referer: http://<app-name>.appspot.com/_ah/upload/AMmfu6ZRpZf67ospmbfJKHd0AKnI9LFkWSDeDuGECy_md0wTVCgPaA9nVuqSg3MUlLJM26dP9I421TDZriqztBSoT7vDEq_Eeel0lhoWwoD1JgFj2pA7bSI/ALBNUaYAAAAATA2SyHej3Q3PwRuq5WJuE0QxgQPHYGMk/ HTTP/1.1 405 Method Not Allowed Server: Upload Server Built on May 19 2010 13:39:25 (1274301565) Allow: POST Date: Tue, 08 Jun 2010 00:36:01 GMT Pragma: no-cache Expires: Fri, 01 Jan 1990 00:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate Content-Length: 0 Content-Type: text/html On Jun 7, 5:10 pm, Jean Hsu <jeanhs...@gmail.com> wrote: > Anyone NOT getting an outOfMemory error? I tried to deploy to > appengine, and don't get an outofmemory error, but instead eventually > get a methodNotFound. Anyone have a small working example? > > Jean > > On Jun 5, 5:22 pm, Luai kassar <luai.kas...@gmail.com> wrote: > > > I am getting OutOfMemoryError too for any file i try to upload . > > can someone explain what the problem is please? > > > Thanks > > Luai. > > > On Jun 3, 12:14 am,JeanHsu <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(UploadBlobServlet.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(UploadBlobServlet.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.
