1) Begging is very unbecoming. Have you tried googling for 'tomcat
java.net.ConnectException'?
2) On the surface, it would appear some of your webapp code is
attempting to connect to another service, but doesn't have the privilege
to do so. If tomcat is running with a security manager, check
Hi
I could resolve the problem. There was incorrect URL mentioned in web.xml of
my application warfile. Actually, i don't deal with configuring this part of
coding -- as i do just administer. And, hence, i did have faith in my
developer who made all changes. After that, the errors were really
Nehal-
If there are 2 people working in your shop say 1 developer and 1 admin
then as the administrator you are the last line of defence before the webapp
is deployed
So if your developer changes the web.xml so that the webapp cannot be
deployed you need to pickup on that and fix it or revert
