Re: [appengine-java] Re: App Engine and Spring slow start up
I do not understand why there is not at least a way to keep the apps running. I would even pay for that. On deck is the ability to pay for and have reserved a warmed instance: http://code.google.com/appengine/docs/roadmap.html (3rd bullet) Baz -- 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.
Re: [appengine-java] Re: App Engine and Spring slow start up
Try using the old way with xml configuration for wiring your beans together. The word on the street is that Spring's component scanning takes a lot of time. luijar wrote: Nope, I am still seeing it. It's quite frustrating. I even tried to reduce Spring init time by removing schema validation from the application context init. But, that does not seem to work. I am using Spring annotations and component scanning to autowire my beans, I wonder if using plain XML configuration will make autowiring faster. On Feb 23, 9:14 pm, charming30 charmin...@gmail.com wrote: Has the above mentioned offline precompilatio in 1.3.1 been able to solve your issue, I plan to use Spring on Java for my Business App which is complex and could be based on SOA. Kindly let me know if your issue was resolved or reduced by using the above fix. On Feb 20, 12:05 am, luijar luis.j.aten...@gmail.com wrote: I believe my development environment was on 1.3.0. That might be something to look at, although it seems that probably it's a very small overhead, do you have any metrics that would give some evidence as to how much overhead is offline precompilation adding? Thanks On Feb 18, 2:04 pm, Don Schwarz schwa...@google.com wrote: Have you deployed your application with the 1.3.1 SDK? That release turned on offline precompilation by default, which is an optimization that may help. On Thu, Feb 18, 2010 at 7:59 AM, Alex chasov...@gmail.com wrote: Hi, It appeared that long init problem is well known for Grails users: http://jira.codehaus.org/browse/GRAILSPLUGINS-1736 I wasted couple of weeks to create app I cannot run. Hope that SpringSource and Google can solve the issue. On Feb 17, 7:41 pm, Stephan Hartmann hartm...@metamesh.de wrote: The problem is that the initialization of your app takes longer than 30 seconds. Pinging your app doesn't help when the app is restarted due to redeployment or maintenance, or when high traffic demands a second instance. You should try to reduce your startup time. regards, Stephan 2010/2/17 luijar luis.j.aten...@gmail.com Great, all of our projects areSpringenabled lol. But I guess it's good that we are not the only ones seeing this, hopefully it gets a little more visibility. We have a cron job (1 min) that tries to keep our application alive by hitting a URL, but it does not do a very good job. It's frustrating and we don't even have access to the 500 page to tell the user to retry or go somewhere else. On Feb 17, 11:21 am, oth other...@gmail.com wrote: Yes we have seen this problem a lot. Per our tests, an application becomes idle after a minute of non activity. So, the unfortunate reality is that you need to keep your app alive by simulating activity on it. Or go the nonSpringroute. Thanks On Feb 16, 4:14 pm, luijar luis.j.aten...@gmail.com wrote: Hello Google App Engine forum, We have been seeing ever since we deployed our applications (currently 3 of them) that when our application instances become idle (they have not been hit for x amount of seconds) subsequent requests return with a 500 response. Logs show a hard deadline exceeded error com.google.apphosting.runtime.HardDeadlineExceededError: This request (32306ebe63b71ab0) started at 2010/02/12 20:39:11.984 UTC and was still executing at 2010/02/12 20:39:41.225 UTC. at com.google.appengine.runtime.Request.process-32306ebe63b71ab0(Request.java) And the first line of the log message has the following : 02-12 12:39PM 14.088 javax.servlet.ServletContext log: InitializingSpringroot WebApplicationContext Question: Has anyone else seen this behavior? How long does it take for an application instance to become idle? Thanks -- You received this message because you are subscribed to the Google Groups Google App Engine forJava 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.comgoogle-appengine-java%2B unsubscr...@googlegroups.com google-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine forJava 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.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 0x2B | ~0x2b -- Hamlet -- 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
Re: [appengine-java] Re: App Engine and Spring slow start up
i got the same problem too, there is no better way to resolve it, i just try to hitting a url with cron job. On Tue, Mar 2, 2010 at 3:50 AM, luijar luis.j.aten...@gmail.com wrote: Thanks for the advice, I'll try that. On Mar 1, 2:31 pm, Rusty Wright rwright.li...@gmail.com wrote: Try using the old way with xml configuration for wiring your beans together. The word on the street is that Spring's component scanning takes a lot of time. luijar wrote: Nope, I am still seeing it. It's quite frustrating. I even tried to reduce Spring init time by removing schema validation from the application context init. But, that does not seem to work. I am using Spring annotations and component scanning to autowire my beans, I wonder if using plain XML configuration will make autowiring faster. On Feb 23, 9:14 pm, charming30 charmin...@gmail.com wrote: Has the above mentioned offline precompilatio in 1.3.1 been able to solve your issue, I plan to use Spring on Java for my Business App which is complex and could be based on SOA. Kindly let me know if your issue was resolved or reduced by using the above fix. On Feb 20, 12:05 am, luijar luis.j.aten...@gmail.com wrote: I believe my development environment was on 1.3.0. That might be something to look at, although it seems that probably it's a very small overhead, do you have any metrics that would give some evidence as to how much overhead is offline precompilation adding? Thanks On Feb 18, 2:04 pm, Don Schwarz schwa...@google.com wrote: Have you deployed your application with the 1.3.1 SDK? That release turned on offline precompilation by default, which is an optimization that may help. On Thu, Feb 18, 2010 at 7:59 AM, Alex chasov...@gmail.com wrote: Hi, It appeared that long init problem is well known for Grails users: http://jira.codehaus.org/browse/GRAILSPLUGINS-1736 I wasted couple of weeks to create app I cannot run. Hope that SpringSource and Google can solve the issue. On Feb 17, 7:41 pm, Stephan Hartmann hartm...@metamesh.de wrote: The problem is that the initialization of your app takes longer than 30 seconds. Pinging your app doesn't help when the app is restarted due to redeployment or maintenance, or when high traffic demands a second instance. You should try to reduce your startup time. regards, Stephan 2010/2/17 luijar luis.j.aten...@gmail.com Great, all of our projects areSpringenabled lol. But I guess it's good that we are not the only ones seeing this, hopefully it gets a little more visibility. We have a cron job (1 min) that tries to keep our application alive by hitting a URL, but it does not do a very good job. It's frustrating and we don't even have access to the 500 page to tell the user to retry or go somewhere else. On Feb 17, 11:21 am, oth other...@gmail.com wrote: Yes we have seen this problem a lot. Per our tests, an application becomes idle after a minute of non activity. So, the unfortunate reality is that you need to keep your app alive by simulating activity on it. Or go the nonSpringroute. Thanks On Feb 16, 4:14 pm, luijar luis.j.aten...@gmail.com wrote: Hello Google App Engine forum, We have been seeing ever since we deployed our applications (currently 3 of them) that when our application instances become idle (they have not been hit for x amount of seconds) subsequent requests return with a 500 response. Logs show a hard deadline exceeded error com.google.apphosting.runtime.HardDeadlineExceededError: This request (32306ebe63b71ab0) started at 2010/02/12 20:39:11.984 UTC and was still executing at 2010/02/12 20:39:41.225 UTC. at com.google.appengine.runtime.Request.process-32306ebe63b71ab0(Request.java) And the first line of the log message has the following : 02-12 12:39PM 14.088 javax.servlet.ServletContext log: InitializingSpringroot WebApplicationContext Question: Has anyone else seen this behavior? How long does it take for an application instance to become idle? Thanks -- You received this message because you are subscribed to the Google Groups Google App Engine forJava 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.comgoogle-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com google-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%252bunsubscr...@googlegroups.com google-appengine-java%252bunsubscr...@googlegroups.comgoogle-appengine-java%25252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google
Re: [appengine-java] Re: App Engine and Spring slow start up
Have you deployed your application with the 1.3.1 SDK? That release turned on offline precompilation by default, which is an optimization that may help. On Thu, Feb 18, 2010 at 7:59 AM, Alex chasov...@gmail.com wrote: Hi, It appeared that long init problem is well known for Grails users: http://jira.codehaus.org/browse/GRAILSPLUGINS-1736 I wasted couple of weeks to create app I cannot run. Hope that SpringSource and Google can solve the issue. On Feb 17, 7:41 pm, Stephan Hartmann hartm...@metamesh.de wrote: The problem is that the initialization of your app takes longer than 30 seconds. Pinging your app doesn't help when the app is restarted due to redeployment or maintenance, or when high traffic demands a second instance. You should try to reduce your startup time. regards, Stephan 2010/2/17 luijar luis.j.aten...@gmail.com Great, all of our projects are Spring enabled lol. But I guess it's good that we are not the only ones seeing this, hopefully it gets a little more visibility. We have a cron job (1 min) that tries to keep our application alive by hitting a URL, but it does not do a very good job. It's frustrating and we don't even have access to the 500 page to tell the user to retry or go somewhere else. On Feb 17, 11:21 am, oth other...@gmail.com wrote: Yes we have seen this problem a lot. Per our tests, an application becomes idle after a minute of non activity. So, the unfortunate reality is that you need to keep your app alive by simulating activity on it. Or go the non Spring route. Thanks On Feb 16, 4:14 pm, luijar luis.j.aten...@gmail.com wrote: Hello Google App Engine forum, We have been seeing ever since we deployed our applications (currently 3 of them) that when our application instances become idle (they have not been hit for x amount of seconds) subsequent requests return with a 500 response. Logs show a hard deadline exceeded error com.google.apphosting.runtime.HardDeadlineExceededError: This request (32306ebe63b71ab0) started at 2010/02/12 20:39:11.984 UTC and was still executing at 2010/02/12 20:39:41.225 UTC. at com.google.appengine.runtime.Request.process-32306ebe63b71ab0(Request.java) And the first line of the log message has the following : 02-12 12:39PM 14.088 javax.servlet.ServletContext log: Initializing Spring root WebApplicationContext Question: Has anyone else seen this behavior? How long does it take for an application instance to become idle? Thanks -- 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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com google-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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.
Re: [appengine-java] Re: App Engine and Spring slow start up
The problem is that the initialization of your app takes longer than 30 seconds. Pinging your app doesn't help when the app is restarted due to redeployment or maintenance, or when high traffic demands a second instance. You should try to reduce your startup time. regards, Stephan 2010/2/17 luijar luis.j.aten...@gmail.com Great, all of our projects are Spring enabled lol. But I guess it's good that we are not the only ones seeing this, hopefully it gets a little more visibility. We have a cron job (1 min) that tries to keep our application alive by hitting a URL, but it does not do a very good job. It's frustrating and we don't even have access to the 500 page to tell the user to retry or go somewhere else. On Feb 17, 11:21 am, oth other...@gmail.com wrote: Yes we have seen this problem a lot. Per our tests, an application becomes idle after a minute of non activity. So, the unfortunate reality is that you need to keep your app alive by simulating activity on it. Or go the non Spring route. Thanks On Feb 16, 4:14 pm, luijar luis.j.aten...@gmail.com wrote: Hello Google App Engine forum, We have been seeing ever since we deployed our applications (currently 3 of them) that when our application instances become idle (they have not been hit for x amount of seconds) subsequent requests return with a 500 response. Logs show a hard deadline exceeded error com.google.apphosting.runtime.HardDeadlineExceededError: This request (32306ebe63b71ab0) started at 2010/02/12 20:39:11.984 UTC and was still executing at 2010/02/12 20:39:41.225 UTC. at com.google.appengine.runtime.Request.process-32306ebe63b71ab0(Request.java) And the first line of the log message has the following : 02-12 12:39PM 14.088 javax.servlet.ServletContext log: Initializing Spring root WebApplicationContext Question: Has anyone else seen this behavior? How long does it take for an application instance to become idle? Thanks -- 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.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- 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.
