Re: Internal error server

On Oct 15, 2004, at 1:32 pm, Nilton Lessa wrote:
> I am in trouble with some apps (most of them are D2W and use Wonder) 
> that are suffering from the "Internal server error 500" error.
>
> The behavior is the following: all runs well, and suddenly the app 
> hangs and Apache returns a 500 error. After this, the app becomes 
> unresponsive and the trustable way to restore the apps is restarting 
> the server...Not a good panorama.
>
You don't see this very often with WO apps, but error 500 usually means 
that the app crashed and returned no contents, which Apache didn't 
like.


> I turned on several logs, from the instances and adaptor. I noticed 
> that I get this error just after the apps are started:(but they start 
> and works apparently well till...500)
>
>
> [2004-10-15 17:13:00 BRST] <main> 
> com.webobjects.foundation.NSForwardException for 
> com.webobjects.foundation.NSForwardException for 
> java.net.BindException: Address already in use
>
This indicates that your app started up before the port that it wants 
to respond to was released.  If your app crashed, it might still be 
holding this port for a minute or so...


sacha


-- 
Sacha Michel Mallais - 400 lb. chimp
Global Village Consulting Inc.:   http://www.global-village.net/
             1. Never tell everything at once.
             -- Ken Venturi, Ken Venturi's Two Great Rules of Life