tomcat-users mailing list archives

Hi,
Not again !!
I ran into the same problem:
SEVERE: Error initializing endpoint
java.net.BindException: Address already in use:8080
at
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:280)
at
org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
at
org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.java:1117)
at
org.apache.catalina.core.StandardService.initialize(StandardService.java:579)
at
org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2246)
not being able to get a clean state.
Can you tell me how to look for status of ports and how I can kill those
processes
keeping thoses port occupied because I can not see tomcat process.
netstat | grep 8080
returns nothing (I get sth. for 8005) but that is not why it fails??!
I do not want to boot everytime I run into that problem ..
Thanks Astrid
Shapira, Yoav wrote:
>Howdy,
>I'm glad you're OK for now ;)
>
>Tomcat shuts down properly under normal circumstances. The only times
>when it doesn't is when webapps start non-daemon threads and don't
>terminate them properly. Sometimes your webapp doesn't do this directly
>but a 3rd party library used by your webapp does.
>
>Yoav Shapira
>Millennium ChemInformatics
>
>
>
>
>>-----Original Message-----
>>From: Astrid Wagner [mailto:Astrid.Wagner@motorola.com]
>>Sent: Monday, September 15, 2003 9:08 AM
>>To: Tomcat Users List
>>Subject: Re: problems starting/stopping tomcat
>>
>>Thanks. We rebooted the machine and until now (I keep my fingers
>>crossed) it works again.
>>Tomcat must have not shut down properly leaving me in a deadlock.
>>Astrid
>>
>>Shapira, Yoav wrote:
>>
>>
>>
>>>Howdy,
>>>Use netstat to see the status of ports.
>>>
>>>Tomcat uses at least two ports at runtime: the SHUTDOWN port (8005 by
>>>default) and the actual user connector ports (8080 and 8009 by default
>>>for tomcat 4.1.x).
>>>
>>>What likely happened was:
>>>- Your first tomcat instance (ports 8005 and 8080) did not shut down
>>>properly, most likely because you had non-daemon threads still
>>>
>>>
>running
>
>
>>>- When you changed to port 8081 and tried to start, you got the error
>>>because tomcat was still listening on port 8005 for shutdown. You
>>>
>>>
>need
>
>
>>>to change both ports, or better yet, fix the cause for tomcat not
>>>shutting down properly ;)
>>>
>>>Yoav Shapira
>>>Millennium ChemInformatics
>>>
>>>
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Astrid Wagner [mailto:Astrid.Wagner@motorola.com]
>>>>Sent: Saturday, September 13, 2003 4:33 AM
>>>>To: tomcat-user@jakarta.apache.org
>>>>Subject: problems starting/stopping tomcat
>>>>
>>>>Hi ,
>>>>I use tomcat 4.1.24, jdk 1.4.0 and Apache 1.3 on Solaris 8.
>>>>After having developed and successfully run many servlets I now
>>>>
>>>>
>receive
>
>
>>>>a "port 8080 already in use problem" after I try to start tomcat.
>>>>
>>>>Sep 13, 2003 10:20:54 AM org.apache.commons.modeler.Registry
>>>>
>>>>
>>>>
>>>>
>>>loadRegistry
>>>
>>>
>>>
>>>
>>>>INFO: Loading registry information
>>>>Sep 13, 2003 10:20:54 AM org.apache.commons.modeler.Registry
>>>>
>>>>
>>>>
>>>>
>>>getRegistry
>>>
>>>
>>>
>>>
>>>>INFO: Creating new Registry instance
>>>>Sep 13, 2003 10:20:57 AM org.apache.commons.modeler.Registry
>>>>
>>>>
>getServer
>
>
>>>>INFO: Creating MBeanServer
>>>>Sep 13, 2003 10:21:00 AM org.apache.coyote.http11.Http11Protocol init
>>>>SEVERE: Error initializing endpoint
>>>>java.net.BindException: Address already in use:8080
>>>> at
>>>>org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoi
>>>>
>>>>
>nt
>
>
>>>>
>>>>
>>>.jav
>>>
>>>
>>>
>>>
>>>>a:280
>>>>)
>>>> at
>>>>org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:150)
>>>>
>>>>
>>>>I did not change any configuration and I do not think that the ports
>>>>are in use by any other processes (Apache uses a different port).
>>>>Could it be that while doing shutdown-startup sequences a process
>>>>has been left hanging (?).
>>>>When I replaced port 8080 by 8081 I was able to start tomcat but when
>>>>
>>>>
>I
>
>
>>>>called a servlet it said "8005" (port for shutdown) in use ?!
>>>>When I replaced also 8005 for test purposes the servlet hangs and I
>>>>could not see any error being logged (catalina.out, web appl log
>>>>
>>>>
>files,
>
>
>>>>Apache log ...).
>>>>
>>>>My question: how do I get more info about what ports tomcat still
>>>>
>>>>
>uses
>
>
>>>>for what ?
>>>>Any hint would be appreciated.
>>>>Thanks.
>>>>
>>>>Astrid
>>>>
>>>>
>>>>
>>>>
>>>
>>>This e-mail, including any attachments, is a confidential business
>>>
>>>
>>communication, and may contain information that is confidential,
>>proprietary and/or privileged. This e-mail is intended only for the
>>individual(s) to whom it is addressed, and may not be saved, copied,
>>printed, disclosed or used by anyone else. If you are not the(an)
>>
>>
>intended
>
>
>>recipient, please immediately delete this e-mail from your computer
>>
>>
>system
>
>
>>and notify the sender. Thank you.
>>
>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>
>
>
>
>This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This e-mail
is intended only for the individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the sender. Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>