> From: Toby Kurien [mailto:[EMAIL PROTECTED]
> Subject: Re: java.lang.Exception: Socket bind failed: [730048]
>
> Only the webserver listening on port 80.

If there's some webserver (which one - IIS?) listening on port 80, then Tomcat 
can't use that port, so it won't be able to initialize as you have it currently 
configured.

> I would like to know if I can kill any process from netstat
> or otherwise (other than from Task Manager, as that doesn't
> show anything useful).

TaskManager is pretty much the only way for Windows (and it does show a lot of 
useful things, such as the PID number).

> For now, I am already rebuilding a new server with Tomcat 6.0 and I
> would like to know if there are any tools to monitor this from
> happening again.

If you want Tomcat to use port 80, then don't start anything else that uses 
port 80.

> I feel Tomcat 6.0 doesn't even have the admin webapp,

It's gone - it had serious internal problems, and no one was interested in 
maintaining it.

> Also any tools to monitor activity, sessions, RAM usage,
> jdbc connections, connection pools would be very helpful.

Look at LambdaProbe, JConsole, and JVisualVM, for freebies that do monitoring 
on the fly.  MoSKito (http://moskito.anotheria.net/) is useful for gathering 
data to be processed later.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to