Web App Port Not Closed When Web App Monitor Closes
Posted: Fri Aug 07, 2009 12:56 pm
by Mike May >> Tue, 24 Jan 2006 12:29:18 GMT
I have a web app, with the usual web app monitor working as a thin client atached to an app server. Occasionally, when I close the web app monitor, the web app service port (the port that the wb app receives requests on) doesn't get closed. (I 'proved' this using netstat - web app monitor closed, jadapp still has the service port open in CLOSE_WAIT state.) Consequently, when I restart the web app monitor, it can't reopen the service port and the browers get the 'Service Unavailable' message.
So - how can I get the service port to close when the web app monitor closes?
I have a web app, with the usual web app monitor working as a thin client atached to an app server. Occasionally, when I close the web app monitor, the web app service port (the port that the wb app receives requests on) doesn't get closed. (I 'proved' this using netstat - web app monitor closed, jadapp still has the service port open in CLOSE_WAIT state.) Consequently, when I restart the web app monitor, it can't reopen the service port and the browers get the 'Service Unavailable' message.
So - how can I get the service port to close when the web app monitor closes?