Hi all.
I'm using Win
NT. I think Tomcat is started, but when I go to the browser, it cannot
find localhost:8080 (or 127.0.0.1:8080).
From an MS_DOS
window I have tried c:\tomcat>bin\startup and also
c:\tomcat\bin>startup. Either way, I then get another window like
this:
Symantec Java!
JustInTime Compiler Version 4.00.006(x) for JDK 1.2 (Symantec
GC)
Copyright (C)
1996-99 Symantec Corporation
Starting tomcat.
Check logs/tomcat.log for error messages
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( /examples )
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( /admin )
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( )
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( /test )
2000-12-14 12:34:26 - PoolTcpConnector: Starting HttpConnectionHandler on 8080
2000-12-14 12:34:26 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( /examples )
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( /admin )
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( )
2000-12-14 12:34:26 - ContextManager: Adding context Ctx( /test )
2000-12-14 12:34:26 - PoolTcpConnector: Starting HttpConnectionHandler on 8080
2000-12-14 12:34:26 - PoolTcpConnector: Starting Ajp12ConnectionHandler on 8007
However, the browser
still gives me the error :
Problem
Report
There was a communication problem.
Message ID TCP_ERROR
Problem Description The system was unable to communicate with the server.
Possible Problem Cause The Web server may be down.
The Web server may be too busy.
The Web server may be experiencing other problems, preventing it from responding to clients.
The communication path may be experiencing problems.
Possible Solution Try connecting to this server later.
Message ID TCP_ERROR
Problem Description The system was unable to communicate with the server.
Possible Problem Cause The Web server may be down.
The Web server may be too busy.
The Web server may be experiencing other problems, preventing it from responding to clients.
The communication path may be experiencing problems.
Possible Solution Try connecting to this server later.
Anybody know what's
going on?
Thanks in
advance.
