1.6.4 dev server not saving data

124 views
Skip to first unread message

Mahron

unread,
Apr 13, 2012, 6:47:45 PM4/13/12
to Google App Engine
Just Rebooted for windows updates and all changes were gone. Not the
First time this happens. It's very annoying and I cant' seem to find a
solution.

I read I was supposed to get "Applying all pending transactions and
saving the datastore" in logs on shutdown.

When I stop the server using the app engine launcher I only get
"(Process exited with code -1)".

Has Anyone had the same problem with 1.6.4 ?

Strom

unread,
Apr 14, 2012, 10:53:12 AM4/14/12
to Google App Engine
How old were the changes? I find that it takes a few minutes for
changes to persist, and this has been the case since forever.

Mahron

unread,
Apr 14, 2012, 12:26:56 PM4/14/12
to Google App Engine
Thanks for the tip, but waiting does not help.

I reinstalled 1.6.3 and now it's working again.
Maybe It was not clear enough but this happens every time the server
is shutdown(not only reboot).

I hope it will be fixed in the next release.

sb

unread,
Apr 14, 2012, 12:53:05 PM4/14/12
to Google App Engine
Having the same problem.

Has been reported.
http://code.google.com/p/googleappengine/issues/detail?id=7244

Kaan Soral

unread,
Apr 14, 2012, 4:19:28 PM4/14/12
to google-a...@googlegroups.com
I had the same problem, since no one reported the problem, I thought it was only me

I solved it by running the DEV_server in administrator mode

If that doesn't solve the problem, switch to sqllite3, its much faster and it works on admin mode (doesn't work for non-admin)

Strange thing is that, when there is no DB file, without admin mode, it creates the DB file, but just can't modify it, on admin mode everything is great

D X

unread,
Apr 15, 2012, 8:28:09 PM4/15/12
to google-a...@googlegroups.com
Yes, this is a 1.6.4 bug.  The datastore now flushes to disk on exit.  The SDK handles two exit signals, but they miss one when you exit from the shell.  I'm not sure if there's other signals that need to be handled on windows as well.

Try this, if it doesn't work there might be another exit signal on windows.  Either that or you're just killing the process without giving it a chance to flush.

Mahron

unread,
Apr 16, 2012, 10:50:19 AM4/16/12
to Google App Engine
I came across that solution before posting. It does not work either.

D X

unread,
Apr 16, 2012, 5:14:14 PM4/16/12
to Google App Engine
Can you provide a bit more info on your dev enviroment? Especially
how you are launching and shutting down dev_appserver?

If you aren't already doing so, try launching dev_appserver from the
command prompt, and shutting it down with Ctrl-C - do you still see
the problem?

Mahron

unread,
Apr 16, 2012, 6:30:30 PM4/16/12
to Google App Engine
Windows 7. I tried using the app engine launcher and also with a .bat
file with the command(which I suppose is the same as command prompt).
I just closed it with the close icon, not ctrl-c if there is any
difference.

I don't need the latest sdk for the moment. I can wait for the next
release. But this needs proper fixing.

D X

unread,
Apr 17, 2012, 10:22:25 PM4/17/12
to google-a...@googlegroups.com
use Ctrl-C to exit.

Mahron

unread,
May 23, 2012, 4:27:48 AM5/23/12
to Google App Engine
Just Installed 1.6.6 and the data is now persistent. Even after sudden
reboot.

I also uninstalled 1.6.3 before installing the new sdk and noticed
1.6.4 was also installed. Maybe the bug came from the installation
process.

So for all those still stuck with 1.6.3 you can give it a try.
Reply all
Reply to author
Forward
0 new messages