Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Tomcat doesn't start, Connection refused

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all, since 3 days i'm trying to work with my new cloud server but Apache Tomcat doesn't start. I've made the some with my old provider and all worked fine, and on my Ubuntu pc and all works fine, but not with this new cloud service. I've tried all ways, can anyone help me? Thank, here is all infos.

1) Cloud server based on Ubuntu 12.04 LTS
2) Java version 1.6.0_24
3) Apache Tomcat 7.0.56
4) The server seems start fine, with the output

but at this point is impossible see the by browser the page http://[ip]:8080, i read a message of impossible connection.
5) But if i try to shutdown it i see

6) The output of catalina.sh run is:


I'm really desperate, if anyone can help me i can send the root data to login on my cloud, to best understand the situation (is not a problem for me, now in the server are only programs and after the operations i can reset the password).

Please... Thank in advance. If needs other infos, i'm here!
 
Ranch Hand
Posts: 10192
3
Mac PPC Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There seems to be an already running server instance on port 8005. The BindException that you see in the server log is the key! Try to kill the process that is running on port 8005 and restart Tomcat again. Hopefully this should cure the situation.
 
Federico Fna
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WOW, thank for your fast reply! I try in 2 minutes!
 
Federico Fna
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
EDIT: If i write sudo netstat -tapen | grep ":8005 "
i see nothing and the terminal give me another prompt row...

and with netstat i see



If you want, i can provide you the credential to my cloud server...
 
Joe Harry
Ranch Hand
Posts: 10192
3
Mac PPC Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Try configuring Tomcat to start on a different port!
 
Federico Fna
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Already done. If i change in conf/server.xml the port 8005 in 8006, such that the file is



i see this



I'm desperate... Do you want check it, with my credentials? I can try to reset the entire cloud, so you can try finding a clear situation... Thank for your help
 
Sheriff
Posts: 4885
317
IntelliJ IDE Python Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Federico, welcome to the Ranch

I edited the title of your thread. Things like "I'm desperate" tend to put people off.
 
Federico Fna
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank, Tim!
 
Saloon Keeper
Posts: 22496
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
According to the Digester report, your server.xml is now defective somewhere around the shutdown="SHUTDOWN" attribute. Possibly you used a word processor to edit it and it inserted a left-double-quote character instead of a symmetric double-quote character.

Port 8005 is the Tomcat control port used by administrative clients to shutdown Tomcat. It's not commonly used for any other application, so I'd keep running netstat and try and see what's grabbing that port. My favorite command usage is "netstat -lnp | grep 8005". Whether sudo is required here, I'm not sure, although it doesn't hurt.

Your original message, however, hints that there's a firewall blocking port 8080. Which is something that your system administrator will have to address. Although Tomcat isn't fully functional with port 8005 unavailable, you could probably still talk to port 8080 if the port wasn't blocked.
 
Federico Fna
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In both case (sudo netstat -lnp | grep 8080, and with 8005) i see another prompt without any message. I thin, this is a provider problem. Maybe i must change it.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic