[appengine-java] Re: Error 500 Expecting a stackmap frame at branch target...

2011-10-25 Thread Mat Jaggard
I resolved this error by manually deleting all my class files (eclipse wasn't always doing this on a "Clean" for some reason) and then recompiling and running using JRE6 instead of JRE7. I have no idea why that was required - maybe some bug in the eclipse java compiler? I wish they'd just use the r

[appengine-java] Re: error 500 from server when starting the guestbook demo app

2009-11-05 Thread Tomas
Yes it was the command search path that needed manual updating. Found help here: http://java.sun.com/javase/6/webnotes/install/jdk/install-windows.html Keep up the good work !! /Tomas On Nov 5, 3:23 pm, Tomas wrote: > Hi Jason ! > The java files are there all right, it seems, and I very recent

[appengine-java] Re: error 500 from server when starting the guestbook demo app

2009-11-04 Thread Jason (Google)
It looks like your system may not have Java configured correctly or otherwise can't invoke the javac compiler needed to compile your application. java.io.IOException: Cannot run program "javac.exe": CreateProcess error=2 You may want to search the web for similar error messages, which might help

[appengine-java] Re: Error 500 deployment

2009-11-02 Thread sproooooz
That was it... Thanks a lot, Steve www.sprosys.com On Sep 19, 11:16 pm, Max Ross wrote: > We've been troubleshooting some index issues.  Can you try one more time? > > Thanks, > Max > > On Sat, Sep 19, 2009 at 3:14 PM, sproz wrote: > > > > > > > I can not deploy my app anymoreusually w

[appengine-java] Re: Error 500 - Loading data to memory during startup

2009-10-26 Thread Jason (Google)
We are working on enhancements that will hopefully reduce this initialization time for cold instances, which should be rolled out with the next couple of releases. There are several other threads on this, and we definitely recognize the importance and appreciate your patience. Regarding the first

[appengine-java] Re: Error 500 - Loading data to memory during startup

2009-10-23 Thread trung
Yeah, AppEngine drops your request after 30 seconds. My app takes 20 seconds to initialize in development, and half of the times it will finish loading within 30 seconds. Other times it goes pass 30 seconds and gets the same 500 error like yours. Google needs to make an exception for the initial

[appengine-java] Re: Error 500 uploading index definitions

2009-09-21 Thread Jason (Google)
Your quotas look fine, including your indices count quota. Can you try uploading one more time? The vacuum_indexes command is currently only available in the Python SDK, but you can still use this command even if you deployed your app using the Java SDK. - Jason On Sat, Sep 19, 2009 at 1:52 PM, W

[appengine-java] Re: Error 500 deployment

2009-09-19 Thread Max Ross
We've been troubleshooting some index issues. Can you try one more time? Thanks, Max On Sat, Sep 19, 2009 at 3:14 PM, sproz wrote: > > I can not deploy my app anymoreusually when it happens I reboot my > computer and it s okbut today it does not work.. > > Here is the message I got:

[appengine-java] Re: Error 500

2009-08-24 Thread HC
Finally , thx. here i made a screen shot for maybe someone who have problem like here. what U need is following this 1. Right click on JRE System Library , and chose properties (http://i61.photobucket.com/albums/h79/hc_reborn/Step1.jpg) 2. Follow the number (http://i61.photobucket.com/a

[appengine-java] Re: Error 500

2009-08-24 Thread Rajeev Dayal
Hi, You can't add a JDK by adding the JDK's bin path to your classpath. What you need to do is go into the Java Build Path dialog, and select the "JRE System Library" entry. Then, click "Edit". A dialog will pop up, giving you the option to select an alternate JRE. However, you probably have not re

[appengine-java] Re: Error 500

2009-08-24 Thread HC
Can U explain with picture step by step ? Sorry i have try ur instruction " By right clicking either on the error in the Problems tab or by right clicking on the project in the package explorer, find Build path. I don't know if the next step was necessary, but under Java Build Path, I included a