[appengine-java] Re: Does AppEngine scale?

[Max]

It seems the limit my colleague was facing related to free version.

30s per request is not issue at all for me.

I think all requests should be simple enough to execute in less then
second.
It is possible to run long running tasks on Amazon EC2 or server in
our office.

On Oct 16, 9:34 pm, Diana Cruise  wrote:
> Max, have you figured out how you will migrate that much data to GAE
> and how long it will take given the 30s limit per request?
>
> On Oct 15, 4:36 pm, Max  wrote:
>
> > Thank You! I see the issue as free status of account.
>
> > Cheers, Max
>
> > On Oct 15, 10:31 am, leszek  wrote:
>
> > >http://code.google.com/appengine/docs/quotas.html
>
> > > --
> > > Requests        1,300,000 requests      7,400 requests/minute   43,000,000
> > > requests        30,000 requests/minute
> > > -
>
> > > Difficult to achieve having one request  simultaneously- Hide quoted text 
> > > -
>
> > - Show quoted text -
>
>
--~--~-~--~~~---~--~~
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: Does AppEngine scale?

[Max]

Thank You!

On Oct 19, 10:42 pm, "Jason (Google)"  wrote:
> Hi Max. It's certainly not a "bad" idea per se, but it will probably take
> some amount of work to move all of this data. If you haven't already, please
> see the documentation on the bulk loader tool -- it's currently only
> available in Python, but you can still use it with your Java apps. It's a
> much better solution than setting a script to import all of your data in
> 30-second increments.
>
> http://code.google.com/appengine/docs/python/tools/uploadingdata.html
>
> As leszek's link points out, applications with billing enabled can handle up
> to 500 requests per second by default, and this can be configured higher if
> your traffic warrants an increase.
>
> - Jason
>
> On Thu, Oct 15, 2009 at 12:01 AM, Max  wrote:
>
> > I thought AppEngine is designed to scale.
> > But recently I heard that AppEngine does not scale.
>
> > Someone benchmarked AppEngine with ab but AppEngine stopped to handle
> > requests after certain level of load. It seems that only one server
> > instance handle requests for 1 user.
>
> > If I will switch to paid account will it scale in case when load
> > jumps?
>
> > I though AppEngine is good choice for sites that may get high traffic.
>
> > 
>
> > 2. We had plans to move one of our databases (6~10 GB) to AppEngine
> > and access it throw REST. Is it a good idea?
>
> > Thanks, Max
>
>
--~--~-~--~~~---~--~~
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: Spring MVC + Sitemesh problem

[Shponter]

Works fine for me too (even with Sitemesh 3).
It took some time and I don't exactly know where the problem was...
I have copied files from the example sitemesh app and evertythig works
fine now.
--~--~-~--~~~---~--~~
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] Request Timeout quota and respons page

[dominity]

Hi, all.

I know that each request to free web application that is deployed at
App Engine server has quota for request execution time. Each time
request executes more than 30 seconds, server responds with standard
error page.
Can I cusomize this page to show user cause of problem?
Or should I handle execution time by myself and interrupt operation
when 30 seconds limit is reached to make respons with web page that
contains usefull information?

Best regards, Alexander.
--~--~-~--~~~---~--~~
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: How much time should it take to upload(deploy) a new version of an application?

[pradeep]

Hi Jason. Thanks for the reply.

But, this is still a problem to me. In my home network, I am behind a
router which might be blocking incoming connections to any
unauthorized ports. Will this be a problem? I am able to upload files
normally to any other site(gmail,etc).
How does this update/deploy work? Any articles available on this, so
that I can debug?

Thanks,
Pradeep.


On Oct 20, 11:42 pm, "Jason (Google)"  wrote:
> That is definitely unusual, even over a slow connection. In general, it
> takes me 10-20 seconds or so depending on the number of modified files
> (using broadband). I haven't heard of any similar issues from other
> developers -- are you sure it's not your network connection/proxy? Can you
> try re-deploying from another network to see if it's any better?
> - Jason
>
>
>
> On Sun, Oct 18, 2009 at 11:19 AM, pradeep  wrote:
>
> > Hi,
> >   It takes me around 2 hours or so to deploy my simple application
> > with 5 jsp s and 2 Java files. Is this normal? Should it take this
> > much time to deploy? I have 128kbps internet connection.
>
> > I tried with appcfg.sh as well as Eclipse plugin.
>
> > Pasting my console:
>
> > sprad...@spradeep-laptop:~/eclipse_goog/plugins/
> > com.google.appengine.eclipse.sdkbundle_1.2.6.v200910130758/appengine-
> > java-sdk-1.2.6/bin$ ./appcfg.sh update /home/spradeep/app/war
> > Reading application configuration data...
> > Beginning server interaction for app-pradeep...
> > 0% Creating staging directory
> > 5% Scanning for jsp files.
> > 8% Compiling jsp files.
> > 11% Compiling java files.
> > 20% Scanning files on local disk.
> > 25% Initiating update.
> > 28% Cloning 3 static files.
> > 31% Cloning 41 application files.
> > 40% Uploading 13 files.
> > <<< > monitor.>>>
> > Uploaded 3 files
> > <<< > monitor.>>>
> > etc
>
> > 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-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] Slowing down local datastore

[WSouza]

Hello,

Is it possible to slow down the local datastore? So it matches more
the performance of the appengine? It would be awesome to add a short
delay on each call to the datastore, so the local debugging/profiling
feels more like the production environment.
--~--~-~--~~~---~--~~
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: Exception while trying to run app

[laurent]

I have found that when using eclipse, after upgrading to new version
of app engine / gwt
it helps to use "run --> run configurations". at the very top of the
window it lists some
of the problem found with the configuration and how to fix it. (it
worked for the issue you
just encountered)

On Oct 24, 6:15 pm, Shawn Brown  wrote:
> seehttp://tinyurl.com/yzhwl6p
>
> It's a known issue with upgrading.  Look at the top result.
--~--~-~--~~~---~--~~
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: Exception while trying to run app

[maksud]

Sometimes I need to copy newer libs into my war/web-inf/lib folder. Creating
a new project ensures that automatically. But old projects does not copy the
newer jars there. So I do a manual copy.

μακσυδ
http://www.commlinkinfotech.com/~maksud


On Mon, Oct 26, 2009 at 12:31 AM, laurent  wrote:

>
> I have found that when using eclipse, after upgrading to new version
> of app engine / gwt
> it helps to use "run --> run configurations". at the very top of the
> window it lists some
> of the problem found with the configuration and how to fix it. (it
> worked for the issue you
> just encountered)
>
> On Oct 24, 6:15 pm, Shawn Brown  wrote:
> > seehttp://tinyurl.com/yzhwl6p
> >
> > It's a known issue with upgrading.  Look at the top result.
> >
>

--~--~-~--~~~---~--~~
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: Exception while trying to run app

[Kyle Roche]

Go to Project / Properties / Run / Debug Settings.

>From there open the AppEngine Service Launch Configurations. You need use
javaagent now. This is what I have. That should fix old projects w/out
having to do anything. Add it to "VM arguments"
-javaagent:/eclipse/plugins/com.google.appengine.eclipse.sdkbundle_1.2.6.v200910130758/appengine-java-sdk-1.2.6/lib/agent/appengine-agent.jar



On Sun, Oct 25, 2009 at 12:06 PM, maksud  wrote:

> Sometimes I need to copy newer libs into my war/web-inf/lib folder.
> Creating a new project ensures that automatically. But old projects does not
> copy the newer jars there. So I do a manual copy.
>
> μακσυδ
> http://www.commlinkinfotech.com/~maksud
>
>
>
> On Mon, Oct 26, 2009 at 12:31 AM, laurent  wrote:
>
>>
>> I have found that when using eclipse, after upgrading to new version
>> of app engine / gwt
>> it helps to use "run --> run configurations". at the very top of the
>> window it lists some
>> of the problem found with the configuration and how to fix it. (it
>> worked for the issue you
>> just encountered)
>>
>> On Oct 24, 6:15 pm, Shawn Brown  wrote:
>> > seehttp://tinyurl.com/yzhwl6p
>> >
>> > It's a known issue with upgrading.  Look at the top result.
>>
>>
>
> >
>

--~--~-~--~~~---~--~~
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: null User from datastore

[Brian Harris]

Yep that was it, thanks.

On Fri, Oct 23, 2009 at 12:54 PM, Jason (Google) wrote:

> Hi Brian. This might be related to JDO fetch groups. Try annotating your
> User field with this, and see if it works:
>
> @Persistent(defaultFetchGroup = "true")
> User myUser;
>
> - Jason
>
> On Wed, Oct 21, 2009 at 9:48 PM, Brian  wrote:
>
>>
>> In development mode, when I query out my entities using JDOQL, they
>> come back with null User fields.  The Datastore Viewer shows a non-
>> null user field, however.
>>
>> I tried importing them with like so, but it didn't help.
>> query.declareImports("import com.google.appengine.api.users.User");
>>
>> Thanks for any ideas,
>> Brian
>>
>>
>>
>
> >
>

--~--~-~--~~~---~--~~
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] Performance difference between local dev server and App Engine

[Nate Drake]

I'm working on a fairly basic App Engine app.  It receives AMF
messages (using OpenAMF) from a Flash app and saves the data in the
data store.  When I run the app using the development server, it takes
100-300 milliseconds to create/update data in the local datastore.
When I deploy it to app engine, it usually takes 3-4 seconds to do the
same thing.  I'm wondering if this performance difference is to be
expected, or if I'm doing something inefficient in my code.

Any advice?

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-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] task queue limit >30 sec?

[sproooooz]

Is the limit duration of a task in a queue superior to 30 seconds?
I receive a DeadlineExceededException all the time
--~--~-~--~~~---~--~~
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] UnsupportedOperationException on a persist/save?

[Rusty Wright]

Any suggestions for how to fix this problem?  I get the following stack trace 
when I use makePersistent() on a class.  It goes away if I add serialized to 
one of its field's annotation; i.e., change the annotation from

@Persistent(defaultFetchGroup = "true", mappedBy = "facility")
private Set waitlistEntries = new HashSet(0);

to

@Persistent(serialized = "true", defaultFetchGroup = "true", mappedBy = 
"facility")
private Set waitlistEntries = new HashSet(0);

This is in the Facility class, the parent class.  Taking out defaultFetchGroup 
and mappedBy doesn't make any difference.

All of the classes that are persisted start with, for example,

@PersistenceCapable(identityType = IdentityType.APPLICATION, detachable = 
"true")
public class WaitlistEntry implements Serializable, Comparable {

All of the other @Persistent annotated fields in the classes are on the 
DataNucleus list (Calendar, Integer, etc.)

When I make the Set of WaitlistEntry serialzed=true then it's not persisted by 
itself and I can't do any queries on it.


java.lang.UnsupportedOperationException
at 
org.datanucleus.store.appengine.EntityUtils.getPropertyName(EntityUtils.java:62)
at 
org.datanucleus.store.appengine.DatastoreFieldManager.getPropertyName(DatastoreFieldManager.java:897)
at 
org.datanucleus.store.appengine.DatastoreFieldManager.storeObjectField(DatastoreFieldManager.java:777)
at 
org.datanucleus.state.AbstractStateManager.providedObjectField(AbstractStateManager.java:1037)
at 
com.objecteffects.waitlist.db.domain.WaitlistEntry.jdoProvideField(WaitlistEntry.java)
at 
com.objecteffects.waitlist.db.domain.WaitlistEntry.jdoProvideFields(WaitlistEntry.java)
at 
org.datanucleus.state.JDOStateManagerImpl.provideFields(JDOStateManagerImpl.java:2715)
at 
org.datanucleus.store.appengine.DatastorePersistenceHandler.insertPreProcess(DatastorePersistenceHandler.java:318)
at 
org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObjects(DatastorePersistenceHandler.java:236)
at 
org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:225)
at 
org.datanucleus.state.JDOStateManagerImpl.internalMakePersistent(JDOStateManagerImpl.java:3185)
at 
org.datanucleus.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImpl.java:3161)
at 
org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.java:1298)
at 
org.datanucleus.sco.SCOUtils.validateObjectForWriting(SCOUtils.java:1476)
at 
org.datanucleus.store.mapped.scostore.ElementContainerStore.validateElementForWriting(ElementContainerStore.java:380)
at 
org.datanucleus.store.mapped.scostore.FKSetStore.add(FKSetStore.java:311)
at 
org.datanucleus.store.mapped.scostore.FKSetStore.addAll(FKSetStore.java:456)
at 
org.datanucleus.store.mapped.mapping.CollectionMapping.postInsert(CollectionMapping.java:157)
at 
org.datanucleus.store.appengine.DatastoreRelationFieldManager.runPostInsertMappingCallbacks(DatastoreRelationFieldManager.java:225)
at 
org.datanucleus.store.appengine.DatastoreRelationFieldManager.access$300(DatastoreRelationFieldManager.java:49)
at 
org.datanucleus.store.appengine.DatastoreRelationFieldManager$1.apply(DatastoreRelationFieldManager.java:112)
at 
org.datanucleus.store.appengine.DatastoreRelationFieldManager.storeRelations(DatastoreRelationFieldManager.java:80)
at 
org.datanucleus.store.appengine.DatastoreFieldManager.storeRelations(DatastoreFieldManager.java:795)
at 
org.datanucleus.store.appengine.DatastorePersistenceHandler.insertPostProcess(DatastorePersistenceHandler.java:288)
at 
org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObjects(DatastorePersistenceHandler.java:241)
at 
org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:225)
at 
org.datanucleus.state.JDOStateManagerImpl.internalMakePersistent(JDOStateManagerImpl.java:3185)
at 
org.datanucleus.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImpl.java:3161)
at 
org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.java:1298)
at 
org.datanucleus.ObjectManagerImpl.persistObject(ObjectManagerImpl.java:1175)
at 
org.datanucleus.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:669)
at 
org.datanucleus.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:694)
at 
com.objecteffects.waitlist.db.impl.dao.jdo.AbstractJdoDao.makePersistent(AbstractJdoDao.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.

[appengine-java] where I should put the Task Queue code?

[Vincent]

It should be a stupid question but I really don't know how to do it ;
(

My understanding is:
just like the Scheduled Tasks With Cron. there is a separated fix-
named xml file to define the target url and schedules. once you
upload, the google app engine can automatically find it and run it.

but how is the Task Queue?
the queue.xml is is only a part of the answer. we need use the
taskqueue to define the target the url and related parameters. just
like below codes:

===
import com.google.appengine.api.labs.taskqueue.Queue;
import com.google.appengine.api.labs.taskqueue.QueueFactory;
import static
com.google.appengine.api.labs.taskqueue.TaskOptions.Builder.*;

// ...
Queue queue = QueueFactory.getDefaultQueue();
queue.add(url("/worker").param("key", key))

=

but where to put these code? I guess it should be another
separated .java file.
but what's name and what's the structure of this file? it's much
appreciated if somebody can share a full example of the task queue
files.


--~--~-~--~~~---~--~~
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: inbound mail encoding problem

[Kyle Roche]

Did you get this worked out? I'm having the same trouble. Also, can't seem
to get the email body still.

Thanks,

On Sat, Oct 24, 2009 at 6:09 AM, Prashant  wrote:

> Hi,
>
> i want to get mail sender's name so i tried *message.getFrom()[0].toString()
> *(followed by trimming out email id), it generally works but for some ids
> i get a weird string like *=?UTF-8?B?QvKYiGd1cyAFeGNlcHRp4pi8bg==?=* i
> know this is some encoding issue but i don't know how to fix this. if anyone
> have any idea please share.
>
>
> 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-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] Storing and managing a collection of objects in a HttpSession.

[fvisticot]

Step1:
My application is using a session to store a collection of objects.
(session configured in GAE deployment file).
session.setAttribute("mySession", new ArrayList());
...
And later:

List objects = (List)session.getAttribute
("mySession");
objects.add(new MyObject());

If i only do this code, the new object added in the list is not stored
in the application.

I need to do a session.setAttribute("mySession", objects); (and with
this setAttribute, the collection is correctly saved).

Step2:
This session is "shared" with an other session (2 PCs with 2
differents browsers).
A sessionManager with a map is in charge to retrieve a
session from the application.

>From the second brower, the session is retrieved but the collection is
empty...

What is the pb ?
How to manage the collection of objects in a session with GAE ? do i
need to use memcache instead of session ?

I assume that the pb is due to multipe JVMs.. but what is the
solution ?


--~--~-~--~~~---~--~~
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: inbound mail encoding problem

[Prashant]

No :( .

For email body, i am still waiting for a working solution.

--~--~-~--~~~---~--~~
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: UnsupportedOperationException on a persist/save?

[Rusty Wright]

Whoops; my mistake.  I had been looking at the DataNucleus documentation rather 
than the Google and I was using an unsupported Calendar when I should have been 
using a Date.


Rusty Wright wrote:
> Any suggestions for how to fix this problem?  I get the following stack 
> trace when I use makePersistent() on a class.  It goes away if I add 
> serialized to one of its field's annotation; i.e., change the annotation 
> from
> 
>@Persistent(defaultFetchGroup = "true", mappedBy = "facility")
>private Set waitlistEntries = new 
> HashSet(0);
> 
> to
> 
>@Persistent(serialized = "true", defaultFetchGroup = "true", mappedBy 
> = "facility")
>private Set waitlistEntries = new 
> HashSet(0);
> 
> This is in the Facility class, the parent class.  Taking out 
> defaultFetchGroup and mappedBy doesn't make any difference.
> 
> All of the classes that are persisted start with, for example,
> 
> @PersistenceCapable(identityType = IdentityType.APPLICATION, detachable 
> = "true")
> public class WaitlistEntry implements Serializable, 
> Comparable {
> 
> All of the other @Persistent annotated fields in the classes are on the 
> DataNucleus list (Calendar, Integer, etc.)
> 
> When I make the Set of WaitlistEntry serialzed=true then it's not 
> persisted by itself and I can't do any queries on it.
> 
> 
> java.lang.UnsupportedOperationException
> at 
> org.datanucleus.store.appengine.EntityUtils.getPropertyName(EntityUtils.java:62)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreFieldManager.getPropertyName(DatastoreFieldManager.java:897)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreFieldManager.storeObjectField(DatastoreFieldManager.java:777)
>  
> 
> at 
> org.datanucleus.state.AbstractStateManager.providedObjectField(AbstractStateManager.java:1037)
>  
> 
> at 
> com.objecteffects.waitlist.db.domain.WaitlistEntry.jdoProvideField(WaitlistEntry.java)
>  
> 
> at 
> com.objecteffects.waitlist.db.domain.WaitlistEntry.jdoProvideFields(WaitlistEntry.java)
>  
> 
> at 
> org.datanucleus.state.JDOStateManagerImpl.provideFields(JDOStateManagerImpl.java:2715)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastorePersistenceHandler.insertPreProcess(DatastorePersistenceHandler.java:318)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObjects(DatastorePersistenceHandler.java:236)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:225)
>  
> 
> at 
> org.datanucleus.state.JDOStateManagerImpl.internalMakePersistent(JDOStateManagerImpl.java:3185)
>  
> 
> at 
> org.datanucleus.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImpl.java:3161)
>  
> 
> at 
> org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.java:1298)
>  
> 
> at 
> org.datanucleus.sco.SCOUtils.validateObjectForWriting(SCOUtils.java:1476)
> at 
> org.datanucleus.store.mapped.scostore.ElementContainerStore.validateElementForWriting(ElementContainerStore.java:380)
>  
> 
> at 
> org.datanucleus.store.mapped.scostore.FKSetStore.add(FKSetStore.java:311)
> at 
> org.datanucleus.store.mapped.scostore.FKSetStore.addAll(FKSetStore.java:456) 
> 
> at 
> org.datanucleus.store.mapped.mapping.CollectionMapping.postInsert(CollectionMapping.java:157)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreRelationFieldManager.runPostInsertMappingCallbacks(DatastoreRelationFieldManager.java:225)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreRelationFieldManager.access$300(DatastoreRelationFieldManager.java:49)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreRelationFieldManager$1.apply(DatastoreRelationFieldManager.java:112)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreRelationFieldManager.storeRelations(DatastoreRelationFieldManager.java:80)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastoreFieldManager.storeRelations(DatastoreFieldManager.java:795)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastorePersistenceHandler.insertPostProcess(DatastorePersistenceHandler.java:288)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObjects(DatastorePersistenceHandler.java:241)
>  
> 
> at 
> org.datanucleus.store.appengine.DatastorePersistenceHandler.insertObject(DatastorePersistenceHandler.java:225)
>  
> 
> at 
> org.datanucleus.state.JDOStateManagerImpl.internalMakePersistent(JDOStateManagerImpl.java:3185)
>  
> 
> at 
> org.datanucleus.state.JDOStateManagerImpl.makePersistent(JDOStateManagerImpl.java:3161)
>  
> 
> at 
> org.datanucleus.ObjectManagerImpl.persistObjectInternal(ObjectManagerImpl.java:1298)
>  
> 
> at 
> org.datanucleus.ObjectManagerImpl.persistObject(ObjectManagerImpl.java:1175) 
> 
> at 
> org.datanucleus.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:669)
>  
> 
> at 
> org.datanucleus.