Hi Andre and Rainer,

thank you for your response. Here is the output of the netstat
command. I filereted them already to the tomcat processes returned.

TCP    0.0.0.0:8088           0.0.0.0:0              LISTENING
6224 [tomcat5.exe]
TCP    0.0.0.0:8109           0.0.0.0:0              LISTENING
6224 [tomcat5.exe]
TCP    0.0.0.0:8188           0.0.0.0:0              LISTENING
7136 [tomcat5.exe]
TCP    0.0.0.0:8209           0.0.0.0:0              LISTENING
7136 [tomcat5.exe]
TCP    0.0.0.0:8288           0.0.0.0:0              LISTENING
4280 [tomcat5.exe]
TCP    0.0.0.0:8309           0.0.0.0:0              LISTENING
4280 [tomcat5.exe]
TCP    0.0.0.0:8388           0.0.0.0:0              LISTENING
4232 [tomcat5.exe]
TCP    0.0.0.0:8409           0.0.0.0:0              LISTENING
4232 [tomcat5.exe]
TCP    127.0.0.1:8005         0.0.0.0:0              LISTENING
6224 [tomcat5.exe]
TCP    127.0.0.1:8105         0.0.0.0:0              LISTENING
7136 [tomcat5.exe]
TCP    127.0.0.1:8205         0.0.0.0:0              LISTENING
4280 [tomcat5.exe]
TCP    127.0.0.1:8305         0.0.0.0:0              LISTENING
4232 [tomcat5.exe]


I tried the command "telnet localhost 8309" the cmd window just
cleared (just a cursor) and nothing came up. no error message. Could
this be a problem with IIS? which crashed? It is just not connecting?


On Sun, Mar 7, 2010 at 2:24 AM, Rainer Jung <rainer.j...@kippdata.de> wrote:
> On 06.03.2010 14:02, Wilmer Tan wrote:
>>
>> Hi,
>>
>> I need help desperately. Our IIS Web Server crashed and since
>> recovery, IIS could no longer connect to Tomcat correctly. The Browser
>> Displays "Service Temporarily Unavailable!"
>> jakarta/ISAPI/isapi_redirect. IIS is working and Tomcat Instances are
>> all running and accessible if I access the port. I cannot find any
>> reference to errno=-9995 from the connector debug. This setup was
>> working before the crash but since then, could not get it to run
>> anymore.
>
> In addition to André's remarks: the -9995 is calculated as
> "WSAGetLastError() - WSABASEERR", where WSABASEERR=10000. So the Original
> error code should have been "5", which is "EIO". Unfortunately there seems
> to be no docs about when a socket call returns an EIO.
>
> Could it be a firewall problem? Are the ports 8109. 8209, 8309, 8409 there
> and can you connect to them?
>
> Regards,
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to