"The full stack trace of the root cause is available in the Apache Tomcat/5.0 logs."
Then please look at the TC logs for the real error and post it here.
monroe wrote:It's hard to say... wandering around the code I found that a key method to this is the WebRequestContext.handleMultipart method. This has a hard coded memory threshold of 100K.
This is also where the tmp directory gets defined from a combination of the ApplicationPath (set up via a request to get the "realpath" for "") and the value of the tmp.dir setting.
The code attempts to make this directory if it can. If that fails it tries to use the OS tmp directory. If ServletExec is reporting something odd for any of these, this might cause this.
Other than that, I'm not sure... especially since you're using a small usage base App Engine like ServletExec.. (I know all J2EE containers are supposed to be equal.. but some are more equal than others...)