Re: Using APR with tomcat leaves port 8009 bound when tomcat is terminated?

On Feb 24, 2006, at 11:15 AM, Jim Jagielski wrote: On Feb 23, 2006, at 11:53 AM, Remy Maucherat wrote: Jim Jagielski wrote: I agree that the change is a big benefit, and for most OSs we care about, SO_REUSEADDR is available. The APR call should gracefully fail... I'll plug this in later on

Re: Using APR with tomcat leaves port 8009 bound when tomcat is terminated?

Jim Jagielski wrote: On Feb 23, 2006, at 11:53 AM, Remy Maucherat wrote: Jim Jagielski wrote: I agree that the change is a big benefit, and for most OSs we care about, SO_REUSEADDR is available. The APR call should gracefully fail... I'll plug this in later on today after some edge-case

Re: Using APR with tomcat leaves port 8009 bound when tomcat is terminated?

D'OH!!! Why doesn't this become an apr_sockattr element to the apr_socket_create or apr_socket_bind call, so that APR determines the before/after thingy? One side note, you setopt *after* the bind if you want to know you are the absolute owner of the socket. you setopt *before* the bind on

RE: Using APR with tomcat leaves port 8009 bound when tomcat is terminated?

. -Original Message- From: Sean Neeley [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 10:59 AM To: Tomcat Users List Subject: RE: Using APR with tomcat leaves port 8009 bound when tomcat is terminated? I built the native connector myself. The platform is Red Hat linux

Re: Using APR with tomcat leaves port 8009 bound when tomcat is terminated?

Jim Jagielski wrote: I agree that the change is a big benefit, and for most OSs we care about, SO_REUSEADDR is available. The APR call should gracefully fail... I'll plug this in later on today after some edge-case tests. In AprEndpoint, there are a lot of Socket.optSet(serverSock,