> It's a common socket programming problem. Usually, one isn't
> too worried about
> it because processes tend to stay alive, keep the socket open
> and bound, and
> listen to subsequent requests, rather than being killed and
> having to restart,
> open and bind a socket. Perhaps some kind of mechanism could
> be written to
> change the port number that the application server uses upon
> every invocation,
> and have some means of the caller (presumably your CGI or Web
> server adapter)
> reading the port number currently in use from some file or
> other service.

Sounds like a lot of trouble to fix something that it seems shouldn't
happen.

> That's if you're that bothered about this. I don't remember
> why this was a
> problem, but if it's for debugging purposes where you just
> want to restart the
> server as quickly as possible then it may not be worth you
> going to this much
> trouble.

Debugging is one of the reasons but more important is trying to
automatically restart the service if it crashes.  I tried using
Monitor.py but it got burned by the fact that AppServer hangs on
restart.

> >Also, the second part of the problem, maybe the real
> problem, is when trying
> >to start the second instance of AppServer, it detects the
> bind failure ok but
> >then hangs as it tries to exit, requiring a kill -9 to end
> it.  Sounds like a
> >thread won't die or something.
>
> That sounds more serious, since it implies that something is
> wrong with the way
> processes or resources are being dealt with. Are there any
> child processes
> attached to the AppServer process? I wonder if there's a way
> of listing the
> resources currently by a hung AppServer process. Does the
> process really hang
> for a long time?

I suspect it hangs forever.  I can't test it right now because I
dropped off the machine at our co-location this morning and am trying
to get a route setup right now.  Once I get that fixed I'll test it
and let you know how long it hangs.


Thanks,
Jeff


_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to