tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 53091] New: Tomcat Server application Not terminating after Bind Exception at Start Up
Date Tue, 17 Apr 2012 11:09:11 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=53091

             Bug #: 53091
           Summary: Tomcat Server application Not terminating after Bind
                    Exception at Start Up
           Product: Tomcat 6
           Version: 6.0.32
          Platform: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: sarthakb@aditi.com
    Classification: Unclassified


We were using tomcat version 4.0.2 for our application with JDK 1.4. Recently
we have upgraded it to version 6.0.32 with JDK 1.6.

After upgradation, we are observing that, if the socket is already blocked on
which tomcat is configured to run, Tomcat is not terminating.

In Version 4.0.2, application use to terminate if any of the port is blocked. 
In Version 6.0.32 application keeps alive even if all the ports are blocked.

Can you please share any configuration so that Tomcat gets terminated on Bind
Exception during start up.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message