netstat -a will determine if Tomcat socket is already bound in which case you will have to stop the server
M- This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents ----- Original Message ----- From: "David Smith" <[EMAIL PROTECTED]> To: "Tomcat Users List" <users@tomcat.apache.org> Sent: Thursday, October 26, 2006 8:50 PM Subject: Re: can not deploy application .war in Tomcat > There has to be more to this error than that. The exception cited has > nothing to do with deploying a .war. Please provide a lot more detail > -- ie os, tomcat version, a complete stack trace, what you did leading > up to this error, ... > > --David > > Shuwen wrote: >> Hi, >> Our own application uses Tomcat as web server. When tomcat is started, it >> should unzip and deploy application .war files. However, we got error: >> >> <<<<<<<<<<<<<<< >> Caused by: java.net.ConnectException: Connection timed out >> at java.net.PlainSocketImpl.socketConnect(Native Method) >> .... >> >> >> I searched on internet and only found that it could be related to firewall >> configuration on the machine. Does anyone know what is the possible cause? >> >> >> Many thanks in advance, >> >> Shuwen >> >> >> --------------------------------- >> Stay in the know. Pulse on the new Yahoo.com. Check it out. >> > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
