Hey all,
I have just discovered something that I didn't realize before. If you
have you have a WO app running inside of Eclipse and Eclipse crashes
the WO app keeps running.
This can cause all sorts of problems. I ended up with three separate
apps running (Eclipse crashed twice) and they were all running the
same scheduled task (via Quartz) so not only was it s...l...o...w
with lots of unexplained DB activity, I was also getting DB errors on
unique-constraints because all three had their own cache of objects
and were each creating the same object.
I had to manually go in and quit the "Java" process in Activity Monitor.
Talk about spending way too much time looking in my code for a bug. I
did, however, end up making my app much more resilient to unexpected
DB changes.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
