[appengine-java] Re: New Mac Java Update, Now Dev Server Stops After ACK Running
Thanks I searched and searched before posting, just wasn't using the right keywords I guess. On Mar 16, 12:55 pm, Jay Young wrote: > https://groups.google.com/forum/#!topic/google-appengine-java/WiImnzV... -- 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-java@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: New Mac Java Update, Now Dev Server Stops After ACK Running
Thanks, I searched and searched before I posted this. Sorry about that. On Mar 16, 12:55 pm, Jay Young wrote: > https://groups.google.com/forum/#!topic/google-appengine-java/WiImnzV... -- 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-java@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] New Mac Java Update, Now Dev Server Stops After ACK Running
My mac just went through series of updates, including a java update. I used to be able to run my dev appengines perfectly on it. Now after 'ant runserver' and it successfully processes everything I get the message, "The server is running at http://localhost:"; it then stops and ant says BUILD SUCCESSFUL. I can run this exact project on another machine (another mac minus the java update though). Anyone seen this / got any ideas? I'd like to change the log reporting level because I feel like something isn't getting through. Thanks, - Mike -- 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-java@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: Application Versions and the Datastore
Thanks Pieter, I knew I had read that in the documentation along time ago but for the life of me I couldn't find it again. On Aug 9, 10:24 am, Pieter Coucke wrote: > All versions of the same app share the same datastore. > > http://code.google.com/appengine/docs/java/javadoc/com/google/appengi... > > "Although Google App Engine allows many versions of your application to be > accessible, there is only one datastore for your application, shared by all > versions. Similarly, the set of indexes is shared by all application > versions." > > > > On Mon, Aug 9, 2010 at 4:12 PM, Mike Dillon wrote: > > Hi all, > > > I was wondering if the different version of the user application code > > base had its own different datastore as well. We just pushed a new > > version onto the app engine and need to re-import our data because of > > some class structure changes. Will the version 1 still keep its > > datastore while we import the data for version 2? > > > Thanks, > > > -Mike > > > -- > > 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 > unsubscr...@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] Application Versions and the Datastore
Hi all, I was wondering if the different version of the user application code base had its own different datastore as well. We just pushed a new version onto the app engine and need to re-import our data because of some class structure changes. Will the version 1 still keep its datastore while we import the data for version 2? Thanks, -Mike -- 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: Java Heap Space Error, Correct Increasing Method?
Thanks Toby, I had figured this out before you replied but didn't
refresh the page before I posted my solution. I appreciate the help!
On Jun 28, 3:59 pm, Toby Reyelts wrote:
> You need to supply --jvm_flag as a command-line argument to dev_appserver.sh
> (aka KickStart), not to java.exe. That should work the same way for the ant,
> task. (You can see this in config/user/ant-macros.xml).
>
>
>
> On Mon, Jun 28, 2010 at 3:51 PM, Mike Dillon wrote:
> > Another thing to consider. I'm not using eclipse, and I'm building and
> > running the server with 'ant runserver'. I just realized that ant
> > isn't calling
> > dev_appserver.sh so I haven't been executing those args at all. When I
> > use dev_appserver.sh to run my server it chokes on --jvm_flag but will
> > run with just the -Xmx, however that has no affect.
>
> > - Mike
>
> > On Jun 28, 2:47 pm, Mike Dillon wrote:
> > > Thanks,
>
> > > Yes that is exactly whats going on, the linux box has 4gb of ram, my
> > > mac has 2gb...
>
> > > And yes I tried the --jvm_flag=-Xmx512m on my mac with no success.
>
> > > - Mike
>
> > > On Jun 28, 2:42 pm, Don Schwarz wrote:
>
> > > > Have you tried --jvm_flag=-Xmxm on your Mac? It should work
> > there
> > > > too.
>
> > > > As for the Linux box, the default heap size is different depending on
> > > > whether you have a "server-class" machine or not, so it is possible
> > that you
> > > > are seeing a much higher default heap size just by virtue of using a
> > machine
> > > > with more RAM or more processors.
>
> > > > The -Xmx setting you added to dev_appserver.sh has no effect. Your
> > code is
> > > > executed in a subprocess, which is why --jvm_flag must be used to pass
> > Java
> > > > args through to this process.
>
> > > > On Mon, Jun 28, 2010 at 6:38 PM, Mike Dillon
> > wrote:
> > > > > Thanks Don,
>
> > > > > I forgot to mention that I'm using a mac with the latest snow leopard
> > > > > update. It seems that these heap space
> > > > > commands are incorrect for my machine, because we just tested it on a
> > > > > linux box and it works fine, even
> > > > > without the --jvm_flag prefix.
>
> > > > > Any ideas?
>
> > > > > - Mike
>
> > > > > On Jun 28, 1:18 pm, Don Schwarz wrote:
> > > > > > I believe you want the following flag:
>
> > > > > > --jvm_flag=-Xmx512m
>
> > > > > > On Sun, Jun 27, 2010 at 3:13 PM, Mike Dillon <
> > mikedillo...@gmail.com>
> > > > > wrote:
> > > > > > > Hello all,
>
> > > > > > > Im working on a project that reads GTFS archives as part of its
> > > > > > > functionality. When we are importing
> > > > > > > a particular set of data that has ~60,000 entries my dev server
> > locks
> > > > > > > up around the 27,000 entry. The
> > > > > > > error is the java heap space error. I would like to know if
> > anyone has
> > > > > > > successfully upped their heap
> > > > > > > space. I searched, and found general instructions but after
> > > > > > > implementing them I'm still failing around
> > > > > > > the same entry. This is leading me to believe that my command
> > line
> > > > > > > args are not taking affect. Here
> > > > > > > is what I have so far:
>
> > > > > > > appengine-sdk-java/bin/dev_appserver.sh:
> > > > > > > #!/bin/bash
> > > > > > > # Launches the development AppServer
> > > > > > > [ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is
> > non-zero
> > > > > > > SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed
> > makes
> > > > > > > absolute
> > > > > > > SDK_LIB=$SDK_BIN/../lib
> > > > > > > SDK_CONFIG=$SDK_BIN/../config/sdk
> > > > > > > java -Xms1024m -Xmx1024m -ea -cp
> > "$SDK_LIB/appengine-tools-api.jar" \
> > > > > > > com.google.appengine.tools.KickStart \
> > > > > > > com.google.appengine.tools.development.DevAppServerMain $*
>
> > > > > > > Is this correct?
[appengine-java] Re: Java Heap Space Error, Correct Increasing Method?
Solved!
Okay here is a quick format for how to increase your java heap space:
If you are running your dev server by running ./dev_appserver.sh then do this:
#!/bin/bash
# Launches the development AppServer
[ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is non-zero
SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed makes
absolute
SDK_LIB=$SDK_BIN/../lib
SDK_CONFIG=$SDK_BIN/../config/sdk
java -ea -cp "$SDK_LIB/appengine-tools-api.jar" \
com.google.appengine.tools.KickStart \
com.google.appengine.tools.development.DevAppServerMain --jvm_flag=-
Xmx $*
*** Notice where the --jvm_flag is !
If you are using ant runserver then you need to edit appengine-sdk-
java/config/user/ang-macros.xml :
Find this, and add an arg value:
Thanks for the help Don.
- Mike
On Jun 28, 3:51 pm, Mike Dillon wrote:
> Another thing to consider. I'm not using eclipse, and I'm building and
> running the server with 'ant runserver'. I just realized that ant
> isn't calling
> dev_appserver.sh so I haven't been executing those args at all. When I
> use dev_appserver.sh to run my server it chokes on --jvm_flag but will
> run with just the -Xmx, however that has no affect.
>
> - Mike
>
> On Jun 28, 2:47 pm, Mike Dillon wrote:
>
>
>
> > Thanks,
>
> > Yes that is exactly whats going on, the linux box has 4gb of ram, my
> > mac has 2gb...
>
> > And yes I tried the --jvm_flag=-Xmx512m on my mac with no success.
>
> > - Mike
>
> > On Jun 28, 2:42 pm, Don Schwarz wrote:
>
> > > Have you tried --jvm_flag=-Xmxm on your Mac? It should work
> > > there
> > > too.
>
> > > As for the Linux box, the default heap size is different depending on
> > > whether you have a "server-class" machine or not, so it is possible that
> > > you
> > > are seeing a much higher default heap size just by virtue of using a
> > > machine
> > > with more RAM or more processors.
>
> > > The -Xmx setting you added to dev_appserver.sh has no effect. Your code
> > > is
> > > executed in a subprocess, which is why --jvm_flag must be used to pass
> > > Java
> > > args through to this process.
>
> > > On Mon, Jun 28, 2010 at 6:38 PM, Mike Dillon
> > > wrote:
> > > > Thanks Don,
>
> > > > I forgot to mention that I'm using a mac with the latest snow leopard
> > > > update. It seems that these heap space
> > > > commands are incorrect for my machine, because we just tested it on a
> > > > linux box and it works fine, even
> > > > without the --jvm_flag prefix.
>
> > > > Any ideas?
>
> > > > - Mike
>
> > > > On Jun 28, 1:18 pm, Don Schwarz wrote:
> > > > > I believe you want the following flag:
>
> > > > > --jvm_flag=-Xmx512m
>
> > > > > On Sun, Jun 27, 2010 at 3:13 PM, Mike Dillon
> > > > wrote:
> > > > > > Hello all,
>
> > > > > > Im working on a project that reads GTFS archives as part of its
> > > > > > functionality. When we are importing
> > > > > > a particular set of data that has ~60,000 entries my dev server
> > > > > > locks
> > > > > > up around the 27,000 entry. The
> > > > > > error is the java heap space error. I would like to know if anyone
> > > > > > has
> > > > > > successfully upped their heap
> > > > > > space. I searched, and found general instructions but after
> > > > > > implementing them I'm still failing around
> > > > > > the same entry. This is leading me to believe that my command line
> > > > > > args are not taking affect. Here
> > > > > > is what I have so far:
>
> > > > > > appengine-sdk-java/bin/dev_appserver.sh:
> > > > > > #!/bin/bash
> > > > > > # Launches the development AppServer
> > > > > > [ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is non-zero
> > > > > > SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed
> > > > > > makes
> > > > > > absolute
> > > > > > SDK_LIB=$SDK_BIN/../lib
> > > > > > SDK_CONFIG=$SDK_BIN/../config/sdk
> > > > > > java -Xms1024m -Xmx1024m -ea -cp
> > > >
[appengine-java] Re: Java Heap Space Error, Correct Increasing Method?
Another thing to consider. I'm not using eclipse, and I'm building and
running the server with 'ant runserver'. I just realized that ant
isn't calling
dev_appserver.sh so I haven't been executing those args at all. When I
use dev_appserver.sh to run my server it chokes on --jvm_flag but will
run with just the -Xmx, however that has no affect.
- Mike
On Jun 28, 2:47 pm, Mike Dillon wrote:
> Thanks,
>
> Yes that is exactly whats going on, the linux box has 4gb of ram, my
> mac has 2gb...
>
> And yes I tried the --jvm_flag=-Xmx512m on my mac with no success.
>
> - Mike
>
> On Jun 28, 2:42 pm, Don Schwarz wrote:
>
>
>
> > Have you tried --jvm_flag=-Xmxm on your Mac? It should work there
> > too.
>
> > As for the Linux box, the default heap size is different depending on
> > whether you have a "server-class" machine or not, so it is possible that you
> > are seeing a much higher default heap size just by virtue of using a machine
> > with more RAM or more processors.
>
> > The -Xmx setting you added to dev_appserver.sh has no effect. Your code is
> > executed in a subprocess, which is why --jvm_flag must be used to pass Java
> > args through to this process.
>
> > On Mon, Jun 28, 2010 at 6:38 PM, Mike Dillon wrote:
> > > Thanks Don,
>
> > > I forgot to mention that I'm using a mac with the latest snow leopard
> > > update. It seems that these heap space
> > > commands are incorrect for my machine, because we just tested it on a
> > > linux box and it works fine, even
> > > without the --jvm_flag prefix.
>
> > > Any ideas?
>
> > > - Mike
>
> > > On Jun 28, 1:18 pm, Don Schwarz wrote:
> > > > I believe you want the following flag:
>
> > > > --jvm_flag=-Xmx512m
>
> > > > On Sun, Jun 27, 2010 at 3:13 PM, Mike Dillon
> > > wrote:
> > > > > Hello all,
>
> > > > > Im working on a project that reads GTFS archives as part of its
> > > > > functionality. When we are importing
> > > > > a particular set of data that has ~60,000 entries my dev server locks
> > > > > up around the 27,000 entry. The
> > > > > error is the java heap space error. I would like to know if anyone has
> > > > > successfully upped their heap
> > > > > space. I searched, and found general instructions but after
> > > > > implementing them I'm still failing around
> > > > > the same entry. This is leading me to believe that my command line
> > > > > args are not taking affect. Here
> > > > > is what I have so far:
>
> > > > > appengine-sdk-java/bin/dev_appserver.sh:
> > > > > #!/bin/bash
> > > > > # Launches the development AppServer
> > > > > [ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is non-zero
> > > > > SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed makes
> > > > > absolute
> > > > > SDK_LIB=$SDK_BIN/../lib
> > > > > SDK_CONFIG=$SDK_BIN/../config/sdk
> > > > > java -Xms1024m -Xmx1024m -ea -cp "$SDK_LIB/appengine-tools-api.jar" \
> > > > > com.google.appengine.tools.KickStart \
> > > > > com.google.appengine.tools.development.DevAppServerMain $*
>
> > > > > Is this correct?
>
> > > > > Also the way we get our data is through a custom import function that
> > > > > chunks the data into groups of 20
> > > > > and then processes them and stores them into the datastore. We are
> > > > > only using one instance of the
> > > > > persistance manager as per the recommendations to use a singleton
> > > > > class. Each batch hits a servlet on
> > > > > our app and then does its work. Should we close the persistence
> > > > > manager after every batch is completed?
> > > > > I'm wondering if this would be a memory leak.
>
> > > > I believe our documentation recommends storing the
> > > PersistenceManagerFactory
> > > > as a singleton, but using a new PersistenceManager each time
> > > > (remembering
> > > to
> > > > close it before discarding).
>
> > > > However, the local implementation of the datastore does keep everything
> > > in
> > > > memory (and simply flushes to disk periodically), so you will run into
> > > size
> > > > issues at some point.
>
> > > --
> > > 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 > > unsubscr...@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: Java Heap Space Error, Correct Increasing Method?
Thanks,
Yes that is exactly whats going on, the linux box has 4gb of ram, my
mac has 2gb...
And yes I tried the --jvm_flag=-Xmx512m on my mac with no success.
- Mike
On Jun 28, 2:42 pm, Don Schwarz wrote:
> Have you tried --jvm_flag=-Xmxm on your Mac? It should work there
> too.
>
> As for the Linux box, the default heap size is different depending on
> whether you have a "server-class" machine or not, so it is possible that you
> are seeing a much higher default heap size just by virtue of using a machine
> with more RAM or more processors.
>
> The -Xmx setting you added to dev_appserver.sh has no effect. Your code is
> executed in a subprocess, which is why --jvm_flag must be used to pass Java
> args through to this process.
>
>
>
> On Mon, Jun 28, 2010 at 6:38 PM, Mike Dillon wrote:
> > Thanks Don,
>
> > I forgot to mention that I'm using a mac with the latest snow leopard
> > update. It seems that these heap space
> > commands are incorrect for my machine, because we just tested it on a
> > linux box and it works fine, even
> > without the --jvm_flag prefix.
>
> > Any ideas?
>
> > - Mike
>
> > On Jun 28, 1:18 pm, Don Schwarz wrote:
> > > I believe you want the following flag:
>
> > > --jvm_flag=-Xmx512m
>
> > > On Sun, Jun 27, 2010 at 3:13 PM, Mike Dillon
> > wrote:
> > > > Hello all,
>
> > > > Im working on a project that reads GTFS archives as part of its
> > > > functionality. When we are importing
> > > > a particular set of data that has ~60,000 entries my dev server locks
> > > > up around the 27,000 entry. The
> > > > error is the java heap space error. I would like to know if anyone has
> > > > successfully upped their heap
> > > > space. I searched, and found general instructions but after
> > > > implementing them I'm still failing around
> > > > the same entry. This is leading me to believe that my command line
> > > > args are not taking affect. Here
> > > > is what I have so far:
>
> > > > appengine-sdk-java/bin/dev_appserver.sh:
> > > > #!/bin/bash
> > > > # Launches the development AppServer
> > > > [ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is non-zero
> > > > SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed makes
> > > > absolute
> > > > SDK_LIB=$SDK_BIN/../lib
> > > > SDK_CONFIG=$SDK_BIN/../config/sdk
> > > > java -Xms1024m -Xmx1024m -ea -cp "$SDK_LIB/appengine-tools-api.jar" \
> > > > com.google.appengine.tools.KickStart \
> > > > com.google.appengine.tools.development.DevAppServerMain $*
>
> > > > Is this correct?
>
> > > > Also the way we get our data is through a custom import function that
> > > > chunks the data into groups of 20
> > > > and then processes them and stores them into the datastore. We are
> > > > only using one instance of the
> > > > persistance manager as per the recommendations to use a singleton
> > > > class. Each batch hits a servlet on
> > > > our app and then does its work. Should we close the persistence
> > > > manager after every batch is completed?
> > > > I'm wondering if this would be a memory leak.
>
> > > I believe our documentation recommends storing the
> > PersistenceManagerFactory
> > > as a singleton, but using a new PersistenceManager each time (remembering
> > to
> > > close it before discarding).
>
> > > However, the local implementation of the datastore does keep everything
> > in
> > > memory (and simply flushes to disk periodically), so you will run into
> > size
> > > issues at some point.
>
> > --
> > 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 > unsubscr...@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: Java Heap Space Error, Correct Increasing Method?
Thanks Don,
I forgot to mention that I'm using a mac with the latest snow leopard
update. It seems that these heap space
commands are incorrect for my machine, because we just tested it on a
linux box and it works fine, even
without the --jvm_flag prefix.
Any ideas?
- Mike
On Jun 28, 1:18 pm, Don Schwarz wrote:
> I believe you want the following flag:
>
> --jvm_flag=-Xmx512m
>
>
>
>
>
> On Sun, Jun 27, 2010 at 3:13 PM, Mike Dillon wrote:
> > Hello all,
>
> > Im working on a project that reads GTFS archives as part of its
> > functionality. When we are importing
> > a particular set of data that has ~60,000 entries my dev server locks
> > up around the 27,000 entry. The
> > error is the java heap space error. I would like to know if anyone has
> > successfully upped their heap
> > space. I searched, and found general instructions but after
> > implementing them I'm still failing around
> > the same entry. This is leading me to believe that my command line
> > args are not taking affect. Here
> > is what I have so far:
>
> > appengine-sdk-java/bin/dev_appserver.sh:
> > #!/bin/bash
> > # Launches the development AppServer
> > [ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is non-zero
> > SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed makes
> > absolute
> > SDK_LIB=$SDK_BIN/../lib
> > SDK_CONFIG=$SDK_BIN/../config/sdk
> > java -Xms1024m -Xmx1024m -ea -cp "$SDK_LIB/appengine-tools-api.jar" \
> > com.google.appengine.tools.KickStart \
> > com.google.appengine.tools.development.DevAppServerMain $*
>
> > Is this correct?
>
> > Also the way we get our data is through a custom import function that
> > chunks the data into groups of 20
> > and then processes them and stores them into the datastore. We are
> > only using one instance of the
> > persistance manager as per the recommendations to use a singleton
> > class. Each batch hits a servlet on
> > our app and then does its work. Should we close the persistence
> > manager after every batch is completed?
> > I'm wondering if this would be a memory leak.
>
> I believe our documentation recommends storing the PersistenceManagerFactory
> as a singleton, but using a new PersistenceManager each time (remembering to
> close it before discarding).
>
> However, the local implementation of the datastore does keep everything in
> memory (and simply flushes to disk periodically), so you will run into size
> issues at some point.
--
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] Java Heap Space Error, Correct Increasing Method?
Hello all,
Im working on a project that reads GTFS archives as part of its
functionality. When we are importing
a particular set of data that has ~60,000 entries my dev server locks
up around the 27,000 entry. The
error is the java heap space error. I would like to know if anyone has
successfully upped their heap
space. I searched, and found general instructions but after
implementing them I'm still failing around
the same entry. This is leading me to believe that my command line
args are not taking affect. Here
is what I have so far:
appengine-sdk-java/bin/dev_appserver.sh:
#!/bin/bash
# Launches the development AppServer
[ -z "${DEBUG}" ] || set -x # trace if $DEBUG env. var. is non-zero
SDK_BIN=`dirname $0 | sed -e "s#^\\([^/]\\)#${PWD}/\\1#"` # sed makes
absolute
SDK_LIB=$SDK_BIN/../lib
SDK_CONFIG=$SDK_BIN/../config/sdk
java -Xms1024m -Xmx1024m -ea -cp "$SDK_LIB/appengine-tools-api.jar" \
com.google.appengine.tools.KickStart \
com.google.appengine.tools.development.DevAppServerMain $*
Is this correct?
Also the way we get our data is through a custom import function that
chunks the data into groups of 20
and then processes them and stores them into the datastore. We are
only using one instance of the
persistance manager as per the recommendations to use a singleton
class. Each batch hits a servlet on
our app and then does its work. Should we close the persistence
manager after every batch is completed?
I'm wondering if this would be a memory leak.
Thanks,
-Mike
--
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: Any ETA for a backup/restore facility?
Mscwd01, I'm not a google employee, but I have had success backing up our datastore and then restoring our datastore with the bulkloader utility. Currently the bulkloader is in the python sdk, so all you need to do is download that and then youll be able to do backups and restore from those backups. Check out the literature on the app engine, and try a couple searches to get your bearings. Nick Johnson has commented or written every search result that comes back when I was researching this a couple of weeks back, and there is also an I/O video on the bulkloader. Make sure you read some of the fine print, i.e. one caveat is that you must have had your datastore populated for at least 12 hours which is the amount of time it takes for the statistics info to be built. That what the bulkloader works off of to do its datastore dump. - Mike On Jun 28, 7:16 am, mscwd01 wrote: > Hey Google Employees, > > There has been a backup/restore facility on the roadmap for a while > now. Can you let us know if and when we may get an in-built tool that > will allow us to easily save the contents of the datastore to our > local machines and restore it if needs be? > > In the meantime, what is the preferred solution to backup/restore our > Java based apps? > > 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.
