🚀 go-pugleaf

Hmm, the machine is not running a firewall, and the port is non-privileged 
(>1024), which is important for *nix.  I think the problem is that no 
process is actually listening, because I ran the command at the command line 
prompt.  Duh.

Anyway, I did that because Tomcat 5 wouldn't run under the debugger and 
there was not error message.  Seems I created a new problem instead.  How 
can I determine what the original problem is?  The status messages 
transition from "server launched" to "process finished" very quickly.

TIA,

Mike


"Lori M Olson [TeamB]" <javadragon@techie.com> wrote in message 
news:42aefb84@newsgroups.borland.com...
> Mike Slinn wrote:
>> I'm having trouble debugging a servlet running under Tomcat.  I copied
>> the command and ran it at a comand line prompt (under Linux) so I could
>> see the problem better:
>>
> When looking at these things, you need to look at the first error, not the 
> last.  The first error is "Connection refused".
>
> Now, remote or local, when you are debugging server-side stuff it is going 
> to make a socket connection to the debugging port, which is specified here 
> as "1162".  The "Connection refused" is telling you that it could not make 
> a connection on port 1162.
>
> This is almost always a firewall issue.  Your machine must be configured 
> to accept connections on the debugging port.  You can change to a 
> different port (one which is not being blocked) or you can alter your 
> firewall settings for port 1162.