My development environment is Windows 7 x64 with Eclipse Kepler x64
What steps will reproduce the problem?
1. Open the guestbook archetype
2. Run unit tests and note the console indicates Master/Slave datastore:
com.google.appengine.api.datastore.dev.LocalDatastoreService init
INFO: Local Datastore initialized:
Type: Master/Slave
Storage: In-memory
3. Modify pom.xml
<plugin>
<groupId>com.google.appengine</groupId>
<artifactId>appengine-maven-plugin</artifactId>
<version>${appengine.target.version}</version>
<configuration>
<jvmFlags>
<jvmFlag>-Ddatastore.default_high_rep_job_policy_unapplied_job_pct=20</jvmFlag>
</jvmFlags>
</configuration>
</plugin>
4. Run unit tests again and note the console still indicates Master/Slave:
com.google.appengine.api.datastore.dev.LocalDatastoreService init
INFO: Local Datastore initialized:
Type: Master/Slave
Storage: In-memory
5. Sanity check by adding datastore configs to the LocalServiceTestHelper(s)
new
LocalDatastoreServiceTestConfig().setDefaultHighRepJobPolicyUnappliedJobPercenta
ge(20)
6. Run tests again and see that they pass with the console indicating High
Replication
com.google.appengine.api.datastore.dev.LocalDatastoreService init
INFO: Local Datastore initialized:
Type: High Replication
Storage: In-memory
I use cross-group transactions, so I need the local datastore to run in High
Replication mode. The LocalDatastoreServiceTestConfig is a workaround for my
tests but I still can not run in Debug mode to test my client.
Thanks for your help.
Extra note: jvm flags -Xdebug and
-Xrunjdwp:transport=dt_socket,address=1044,server=y,suspend=y work as expected
Original issue reported on code.google.com by ste...@lightningrodgames.com on 11 Sep 2013 at 3:37
Original issue reported on code.google.com by
ste...@lightningrodgames.com
on 11 Sep 2013 at 3:37