🚀 go-pugleaf

Mike Slinn wrote:

> 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.

I don't think it's the debugger, as JBuilder is pretty good about
choosing ports that aren't in use.  What it might be is that you have
something else listening on either port 8080 (Tomcat's HTTP port) or
8081 (Tomcat's control port).  Before starting Tomcat, check for
anything listening on port 808X.

-- 
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/

NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html

Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html