• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Deaths = broken pipe?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deaths = broken pipe?


  • Subject: Re: Deaths = broken pipe?
  • From: Lachlan Deck <email@hidden>
  • Date: Sun, 25 Jan 2009 20:47:23 +1100

On 24/01/2009, at 6:11 AM, Kieran Kelleher wrote:

On one slow G4 xserve, I have had situation about once month whereby I get an email (presumably from wotaskd) from the specific server reporting one or two "Deaths" on an instance running on that machine. I look at the time of the email and compare that to the logs, I don't see the usual startup stuff in the log, so it makes me wonder if the app really restarted at all. Secondly, the last entry before the time of a "Death" is usually something like:

WARN 2009-01-23 13:25:49,844 [WorkerThread5] (NSLog: 43) - <WOWorkerThread id=5 socket=Socket[addr=/ 192.168.1.149,port=58070,localport=2001]> Exception while sending response: java.net.SocketException: Broken pipe

If I go look at the WOStats page for the instance it tells me that this instance is up for nearly 7 days, so that would seem to indicate that the app really did not crash and restart ..... also no entry in /Library/Logs/CrashReporter for that time of the "Death".

So my question is if this is a case where the response taking too long is being considered a "Death", but the app is not really dying and being restarted at all?

I am guessing that a user is accessing a specific page that is loading a lot of data and they get a no instance available, but this is not killing the app (BTW, concurrent request handling is on) ... is this the case?

Secondly, I try to determine which page may have broken the pipe by looking at WOStats, but I find most actions have a max of ~2 seconds and perhaps 3 pages have a max of ~11 seconds although their average is less than 1 second, so there is no action near ~30 seconds ... how would I determine the page that caused the broken pipe? .... or should I just focus on ensuring that those pages that did have a high max of ~11 secs get reqorked so their max never exceeds ~2 secs?

Hard one to track down. I find some of our apps after a week or two of being up seem to start having broken pipes .. unless we put them on scheduled restarts. Don't know if there's a slow leak or if it's a db connection issue. Certainly this can happen if there's an OutOfMemory exception.


with regards,
--

Lachlan Deck



_______________________________________________
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


References: 
 >Deaths = broken pipe? (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: Re: Proper way to install Eclipse/WOLips/Wonder
  • Next by Date: Sometime WebObjects drives me a little crazy!
  • Previous by thread: Deaths = broken pipe?
  • Next by thread: Re: Deaths = broken pipe?
  • Index(es):
    • Date
    • Thread