Re: Eclipse Crashes but WOApp Keeps Running
Re: Eclipse Crashes but WOApp Keeps Running
- Subject: Re: Eclipse Crashes but WOApp Keeps Running
- From: Stamenkovic Florijan <email@hidden>
- Date: Thu, 12 Mar 2009 11:56:23 -0400
On Mar 12, 2009, at 11:45, David Avendasora wrote:
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.
Huh, that's good to know. Thinking about it, this could be both a bug
and a feature, from Eclipse's point of view...
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.
However, if you define the port on which the app runs, you can only
have one instance running. Other instances can't start up as the port
is taken. This is useful also in other situations. For example, I
normally run my builds from the cmd line before deploying, because an
app can behave differently if you run it from Eclipse (which I do
during dev). So, if one version is already running, the other will
crash on startup. Thereby, I am 100% sure which app I am connecting to.
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.
:D
F
_______________________________________________
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