[appengine-java] Re: CloudCover: Cannot schedule instance of TestClass because of not an available class
Not sure what the problem is, all my queries are failing with this
message:
Illegal argument
javax.jdo.JDOFatalUserException: Illegal argument at
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:
344) at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:252) at
Environment: SDK 1.3.4
JUnit = 4
Is there a code sample we can use as reference?, with all of the
required JAR files?. I haven't been able to run a single test that
requires accessing datastore.
On Jun 30, 5:58 pm, luijar luis.j.aten...@gmail.com wrote:
I am seeing this however,
Executing a simple query:
Illegal argument
javax.jdo.JDOFatalUserException: Illegal argument at
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:
344) at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:252) at
This query works when the actual application is running, and it works
in the Local testing Helper, but not with the
CloudCoverLocalServiceTestHelper. Is there a specific version of App
Engine I should be using? I am using 1.3.2.
On Jun 12, 11:57 pm, Max Ross (Google) maxr+appeng...@google.com
wrote:
This most likely means that your tests aren't available as part of your
application. Are you certain you uploaded them?
On Fri, Jun 11, 2010 at 11:31 PM, Art art...@gmail.com wrote:
Dear group,
I would like to know how to make CloudCover (http://code.google.com/p/
cloudcover/) work.
At cloudcover.html, even I clicked on the Start New Run button, the
(default) test won't be executed.
The cloudcover.html showed like:
Run 1001: NOT_STARTED, Completed 0/0 (0%)
Passed: 0 Too Slow: 0 Failed: 0 In Progress: 0 Not Started: 0
com.google.appengine.testing.cloudcover.harness.junit3.JUnit3TestHarness
(0)
I found the following logs in the GAE/J logs:
W 06-11 10:45PM 49.387
com.google.appengine.testing.cloudcover.harness.junitx.JUnitTestRun
getTestIds: 1001: Cannot schedule instance of class
com.appspot.waversbeach.server.MemcacheTest for execution because its
String represenation,
testInsert1(com.appspot.waversbeach.server.MemcacheTest), is not an
available class.
W 06-11 10:45PM 49.395
com.google.appengine.testing.cloudcover.harness.junitx.JUnitTestRun
getTestIds: 1001: Cannot schedule instance of class
com.appspot.waversbeach.server.MemcacheTest for execution because its
String represenation,
testInsert2(com.appspot.waversbeach.server.MemcacheTest), is not an
available class.
MemcacheTest class is a really simple test class just for the trial
purpose with CloudCover:
public class MemcacheTest extends TestCase {
public MemcacheTest( String name) {
super( name);
}
protected static Cache cache = null;
�...@override
protected void setUp() throws Exception {
if ( cache == null) {
CacheFactory cacheFactory =
CacheManager.getInstance().getCacheFactory();
cache = cacheFactory.createCache(
Collections.emptyMap());
}
}
�...@override
protected void tearDown() throws Exception {
cache.clear();
}
private void doTest() {
assertFalse( cache.containsKey( yar));
cache.put( yar, foo);
assertTrue( cache.containsKey( yar));
}
public void testInsert1() {
doTest();
}
public void testInsert2() {
doTest();
}
}
My JUnit3Config class is like:
public class CloudCoverRunnerConfig extends JUnit3Config {
�...@override
public TestRun newTestRun( String arg0) {
TestSuite suite = new TestSuite();
suite.addTest( new MemcacheTest( testInsert1));
suite.addTest( new MemcacheTest( testInsert2));
return new JUnit3TestRun( suite);
}
}
I'm thinking of giving the CloudCover a shot for Wave robot testing if
it's possible, since I have read in one of Wave docs that there is no
existing mechanism currently to test Wave robot on local machine.
Thank you
--
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
[appengine-java] App Engine Down?
We just experienced an outtage that seems to be from Google App Engine for one of our registered app ID's. It lasted for several hours and it seems to be back up again without us making any changes. Has anyone else experienced this? If so, what was the cause? -- 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.
[appengine-java] Re: App Engine Down?
8:55AM Pacific was the last error we saw. Basically, it was throwing DeadlineExceededExceptions quickly all of the time. On Apr 27, 12:11 pm, luijar luis.j.aten...@gmail.com wrote: We just experienced an outtage that seems to be from Google App Engine for one of our registered app ID's. It lasted for several hours and it seems to be back up again without us making any changes. Has anyone else experienced this? If so, what was the cause? -- 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 athttp://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.
[appengine-java] Re: App Engine and Spring slow start up
Thanks Toby, Can you point me to the threads you talk about? Thanks, Luijar On Mar 2, 4:15 am, Toby toby.ro...@gmail.com wrote: Hi luijar, I had the same problem -but no time-out- and I got some better performance by removing all autowire and annotation-scan stuff and also by putting lazy-init=true on my beans. I even re-wrote a bean by a regular Servlet, without any Spring and the startup performance was as poor as with using spring. So I think the initialization overhead is not that big.Depends a lot on your application, though. What is the worst is that even once an instance is started up, it immediately seems to be suspended again. I think the cron-job is probably not the best way to do it even though it seems the only posibility for the moment. You will find a lot of threads on this topic. Toby On Mar 2, 3:27 am, yjun hu itswa...@gmail.com wrote: 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
[appengine-java] Re: App Engine and Spring slow start up
I think it's insane that it takes this long: org.springframework.web.context.ContextLoader initWebApplicationContext: Root WebApplicationContext: initialization completed in 17914 ms The only reason I haven't taken Spring out and use Struts for MVC and Guice for DI (or equivalent technologies) is that I am also using Spring AOP, which I suspect adds a lot of overhead to the mix. On Mar 3, 5:18 pm, luijar luis.j.aten...@gmail.com wrote: Thanks Toby, Can you point me to the threads you talk about? Thanks, Luijar On Mar 2, 4:15 am, Toby toby.ro...@gmail.com wrote: Hi luijar, I had the same problem -but no time-out- and I got some better performance by removing all autowire and annotation-scan stuff and also by putting lazy-init=true on my beans. I even re-wrote a bean by a regular Servlet, without any Spring and the startup performance was as poor as with using spring. So I think the initialization overhead is not that big.Depends a lot on your application, though. What is the worst is that even once an instance is started up, it immediately seems to be suspended again. I think the cron-job is probably not the best way to do it even though it seems the only posibility for the moment. You will find a lot of threads on this topic. Toby On Mar 2, 3:27 am, yjun hu itswa...@gmail.com wrote: 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
[appengine-java] Re: App Engine and Spring slow start up
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%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
[appengine-java] Re: App Engine and Spring slow start up
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. -- You
[appengine-java] Re: App Engine and Spring slow start up
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 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.
[appengine-java] Re: App Engine and Spring slow start up
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.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] App Engine and Spring slow start up
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.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Exception When Uploading Application To AppEngine
I am beginning to see this problem when uploading my application to the AppEngine. Here is the stack trace: com.google.appengine.tools.admin.AdminException: Unable to update app: Error writing to server at com.google.appengine.tools.admin.AppAdminImpl.update (AppAdminImpl.java:62) at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy (AppEngineBridgeImpl.java:271) at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace (DeployProjectJob.java:148) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run (InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: Error writing to server at sun.reflect.GeneratedConstructorAccessor169.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException (Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at java.net.HttpURLConnection.getResponseCode(Unknown Source) at com.google.appengine.tools.admin.ServerConnection.send (ServerConnection.java:129) at com.google.appengine.tools.admin.ServerConnection.post (ServerConnection.java:95) at com.google.appengine.tools.admin.AppVersionUpload.send (AppVersionUpload.java:432) at com.google.appengine.tools.admin.AppVersionUpload.uploadFile (AppVersionUpload.java:335) at com.google.appengine.tools.admin.AppVersionUpload.doUpload (AppVersionUpload.java:105) at com.google.appengine.tools.admin.AppAdminImpl.update (AppAdminImpl.java:56) ... 4 more I don't know what the cause of this may be, I am seeing it with two of our apps that we created. We have been able to upload in the past every time without any problems, and since we started seeing this error, we have not been able to upload. I have even tried deleting the entire src folder and deploying, no luck. Creating a simple test application through Eclipse works just fine. We have tried uploading with both the appCfg tool and Eclipse, same error. We have experienced this with AppEngine 1.2.2 and 1.2.6. These are the steps that happen every time: After successful compilation of GWT... Compilation succeeded -- 14.631s Creating staging directory Scanning for jsp files. Scanning files on local disk. Scanned 250 files. Scanned 500 files. Scanned 750 files. Scanned 1000 files. Initiating update. Cloning 284 static files. Cloned 100 files. Cloned 200 files. Cloning 747 application files. Cloned 100 files. Cloned 200 files. Cloned 300 files. Cloned 400 files. Cloned 500 files. Cloned 600 files. Cloned 700 files. Uploading 43 files. Rolling back the update. java.io.IOException: Error writing to server Has anybody seen anything similar? Please help -- 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=.
