tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Turoff <stevetur...@home.com>
Subject RE: Restarting Tomcat on NT - Solved
Date Sun, 15 Jul 2001 04:45:09 GMT
Turning off ZoneAlarm solved the problem.

Steve

At 06:47 PM 07/03/2001, you wrote:
>Darrell,
>
>I can't think of any apps I'm running that have integrated web servers. 
>Perhaps mySQL? Maybe my firewall (ZoneAlarm)? Emacs?
>
>Steve
>
>At 02:56 PM 07/03/2001, Darrell Porter wrote:
>>Steve,
>>
>>If you're running personal web server, IIS, or some third party apps that
>>have integrated web servers (several webcam products come to mind), then
>>shut these down.  This is most likely the offending application.
>>
>>Darrell
>>
>>
>>-----Original Message-----
>>From: Steven Turoff [mailto:steveturoff@home.com]
>>Sent: Tuesday, July 03, 2001 5:30 AM
>>To: tomcat-user@jakarta.apache.org
>>Subject: RE: Restarting Tomcat on NT
>>
>>
>>Actually, I'm not running Tomcat as a service. I meant that I don't have
>>any problems starting Tomcat after rebooting the machine. I've run netstat
>>-a (results below) and can see that the ports are in use, however that
>>information doesn't seem to be very useful. Perhaps I should try running
>>tomcat as a service?
>>
>>Steve
>>
>>At 05:56 AM 07/03/2001, Randy Layman wrote:
>>
>> >         No, there is no way to free a port.  You mentioned that Tomcat
>>comes
>> >up after a reboot, implying that you are running Tomcat as a service.  If
>> >that is the case, the process name is jk_nt_service.exe.  Unless you have
>> >another process that is constantly trying to grab that port, Tomcat is
>>still
>> >running - NT does free the ports when the process dies.
>> >
>> >         Also, 2000 (and I believe NT) ship with netstat.  Using "netstat
>>-a"
>> >you can determine which ports are currently in use (and their state).
>> >
>> >         Randy
>> >
>> > > -----Original Message-----
>> > > From: Steven Turoff [mailto:steveturoff@home.com]
>> > > Sent: Monday, July 02, 2001 7:34 PM
>> > > To: tomcat-user@jakarta.apache.org
>> > > Subject: RE: Restarting Tomcat on NT
>> > >
>> > >
>> > > I've already tried that. Tomcat is dead, alright. Is there a way to
>> > > explicitly free up a port on NT?
>> > >
>> > > At 06:04 PM 07/02/2001, you wrote:
>> > > >Maybe you didn't really kill off Tomcat, but just the DOS
>> > > box it was running
>> > > >in,...  (I've seen it happen after closing the DOS box, but not after
>> > > >Ctrl+C'ing the program.)
>> > > >
>> > > >Try bringing up the Task Manager, and make sure there aren't
>> > > any instances
>> > > >of a "java" image name running.
>> > > >
>> > > >                                         -- Bill K.
>> > > >
>> > > > > -----Original Message-----
>> > > > > From: Steven Turoff [mailto:steveturoff@home.com]
>> > > > > Sent: Monday, July 02, 2001 3:30 PM
>> > > > > To: tomcat-user@jakarta.apache.org
>> > > > > Subject: Restarting Tomcat on NT
>> > > > >
>> > > > >
>> > > > > I am having problems restarting Tomcat on NT. After a
>> > > reboot of the
>> > > > > machine, Tomcat starts without a problem. However, if I stop
>> > > > > Tomcat and
>> > > > > then attempt to restart, I get the following error:
>> > > > >
>> > > > > FATAL:java.net.BindException: Address in use: bind
>> > > > > java.net.BindException: Address in use: bind
>> > > > >          at java.net.PlainSocketImpl.socketBind(Native Method)
>> > > > >          at
>> > > java.net.PlainSocketImpl.bind(PlainSocketImpl.java:390)
>> > > > >          at java.net.ServerSocket.<init>(ServerSocket.java:173)
>> > > > >          at java.net.ServerSocket.<init>(ServerSocket.java:124)
>> > > > >          at
>> > > > > org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(
>> > > > > DefaultServerSocketFactory.java:97)
>> > > > >          at
>> > > > > org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint(PoolTc
>> > > > > pEndpoint.java:239)
>> > > > >          at
>> > > > > org.apache.tomcat.service.PoolTcpConnector.start(PoolTcpConnec
>> > > > > tor.java,
>> > > > > Compiled Code)
>> > > > >          at
>> > > > > org.apache.tomcat.core.ContextManager.start(ContextManager.jav
>> > > > > a, Compiled Code)
>> > > > >          at
>> > > org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:202)
>> > > > >          at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235)
>> > > > >
>> > > > > I'm running Tomcat on port 8080. After I receive the above
>> > > > > error, a netstat
>> > > > > -a yields:
>> > > > >
>> > > > >    TCP    cx628443-b:8007        0.0.0.0:0              LISTENING
>> > > > >    TCP    cx628443-b:8007        0.0.0.0:0              LISTENING
>> > > > >    TCP    cx628443-b:8080        0.0.0.0:0              LISTENING
>> > > > >    TCP    cx628443-b:8080        0.0.0.0:0              LISTENING
>> > > > >
>> > > > > So, for some reason, stopping Tomcat does not free up the
>> > > > > port. I must then
>> > > > > reboot my machine to run Tomcat again. I'm using Tomcat 3.2.1
>> > > > > and Classic
>> > > > > VM (build JDK-1.2.2-001, native threads, symcjit).
>> > > > >
>> > > > > Ideally, I'd like to fix the problem, however, I'm also
>> > > > > interested in any
>> > > > > solution that doesn't require rebooting my machine. I'll be
>> > > > > switching to a
>> > > > > Linux-Tomcat platform soon, but need a solution for the meantime.
>> > > > >
>> > > > > Thanks,
>> > > > >
>> > > > > Steve
>> > > > >
>> > >


Mime
View raw message