Re: Eclipse Crashes but WOApp Keeps Running
Re: Eclipse Crashes but WOApp Keeps Running
- Subject: Re: Eclipse Crashes but WOApp Keeps Running
- From: Kieran Kelleher <email@hidden>
- Date: Thu, 12 Mar 2009 11:58:58 -0400
Hi David,
Use a fixed WOPort in your run/debug configuration to avoid this ....
and you get bookmarkable URLs as a bonus too ;-)
Kieran
On Mar 12, 2009, at 11:45 AM, David Avendasora wrote:
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@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden