You can not change the timeout. One possible solution might be to load the data incrementally. Application instances might be created and destroyed at any time, so you would need to be sure your app can handle re-initializing itself when needed.
Perhaps if you posted some additional details someone might be able to suggest alternative implementations. Robert On Thu, Feb 4, 2010 at 6:24 AM, Alyona <[email protected]> wrote: > Hi, > > I have posted a question about a 500 Server error yesterday in the > Java forum: > http://groups.google.com/group/google-appengine-java/browse_thread/thread/143be797f68dae82 > > Since then I realized that the problem is in the timeout request. > The timeout happens in the initialization stage of the web server, > where I'm loading several MB of text data into the main memory. This > is a requirement by my application. > Once initialized, I expect the requests to be small and fast. > > I found that there is a 30sec timeout for any server activity. Is it > possible to change it or to set a specific timeout for initialization? > Or is my kind of app not suitable to be run on Google App Engine? > > Thanks in advance for your answer > Alyona > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
