> The problem still occurs even if we turn logging off completely, so it seems > unlikely that that's the issue.
By logging I meant my own logging, opening/closing file handles myself. Not ns_log or access log, etc. There used to be a command, I forget what now, which would return a list of currently running threads and some info about them. Maybe you could look at that, see if there's anything interesting. I'd recommend having a scheduled proc run once a minute or so, outputting somewhere, since you mentioned that scheduled procs still worked. > Bouncing AOLServer clears things up, which makes me wonder about the Oracle > idea. It's worth a look, though. I think that worked for us too. I wish I'd taken more note. The problems stopped, and I stopped worrying. This was more like the 3.0 or 3.1 days as well. > One other interesting thing to note is that scheduled procs continue to > operate normally. So the server is alive inside. It just doesn't serve up > any pages. That makes me think this is something external to aolserver, something is grabbing the port. I know it sounds dumb, but is there anything else running? Apache, something else? I wondered when I had these problems if *oracle* wasn't grabbing the port. But I don't know. Could this result from some deadlock condition? a mutex problem, whether in your code, or inherent in aolserver? Rusty ------------------------------------------ Rusty Brooks : http://www.rustybrooks.org/ Spewing wisdom from every orifice ------------------------------------------
