Re: Cant reenter deployed application after an uncaught exception.
Re: Cant reenter deployed application after an uncaught exception.
- Subject: Re: Cant reenter deployed application after an uncaught exception.
- From: Zac Konopa <email@hidden>
- Date: Mon, 26 Jun 2006 09:19:29 -0700
Both excellent questions. As to the first I'm afraid I don't have an
exception backtrace. Since is a "deployment" build it's hiding the
back trace automatically. I'm doing the research to figure out how
to turn that off today. JavaMonitor has not been able to restart the
app so your editing context deadlock exception sounds quite
plausible. I'm not familiar with this though can you explain a
little more? As for locking and unlocking an editing context, here
goes. I follow the following guidelines whenever I'm working with an
editing context. First I use instance variables to store form values
and such for validation. After the data has been validated I lock
the editing context, instantiate my record, assign the values from my
instance variables, insert the object into the ec, and when
appropriate I save the changes to the ec. Sometimes it's a long and
complicated process of inserting to the save changes step is saved
till later when the user can confirm the input. After the insert and
save step the ec is unlocked. Now that I think about it I like this
deadlocked ec idea a lot because I have essentially no exception
handling at this point, and I happen to know what is throwing the
exception and that it would happen before the ec was unlocked.
However what would cause this to change from a dev build to a deploy
build?
thanks for the help.
Zac
On Jun 23, 2006, at 6:53 PM, Art Isbell wrote:
On Jun 23, 2006, at 3:16 PM, Zac Konopa wrote:
All right gang heres a challenge. I'm beta testing an app.
Whenever I deploy the application if there is an uncaught
exception the app apparently locks up and wont respond to any
other attempts to access it.
What is the uncaught exception? Do you have an exception backtrace?
By which I mean you can't reenter the app by clicking the link on
the default error screen, and I can't just open another browser
window to the app, it just doesn't respond.
Can JavaMonitor restart it without force quitting it? If not, it
could be deadlocked. Are you locking/unlocking all editing
contexts except Session's default editing context? Are you using a
shared editing context and locking/unlocking when not using those
methods documented to be safe?
Aloha,
Art
_______________________________________________
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