Re: analysing a production failure
Re: analysing a production failure
- Subject: Re: analysing a production failure
- From: Chuck Hill <email@hidden>
- Date: Fri, 16 Oct 2009 14:13:22 -0700
On Oct 16, 2009, at 1:56 AM, Simon McLean wrote:
Hi Chuck - Good holiday ?
In Quebec? Yes, wonderful. I highly recommend it! Great food,
wonderful hosts, interesting history etc. I am looking forward to
going back next year.
2) why would a problem with one host start knocking out other hosts?
Bad coding in JavaMonitor? Bad config getting sent to the other
hosts due to mishandling of an exception somewhere?
Right, of course. if JavaMonitor splattered a duff config around
then that would explain things.
What's really concerning me is we had another JavaMonitor related
issue 5 days ago. After updating our apps, one of them just would
not restart. In the end we had to delete this one app's
configuration from JavaMonitor and rebuild it, then it started up
fine. In other words it looked like JavaMonitor had screwed up this
one apps configuration - which is rather worrying.
I've very rarely seen it do that. My recollection is that it writes
out invalid XML which it then can't read.
The source for both is in Wonder, so fixes can be made.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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