#394 new

Webrick not stopped when using rack application server

Reported by ess | August 31st, 2010 @ 04:55 AM

Sorry for the superfluous pull request.

Using 0.7.2.beta.1 and the rack application server, it appears that webrick instances are not actually killed, as it raises an error on SIGTERM. The following commits use SIGINT instead (known to properly shut down webrick, at the least) and add a wait for socket destruction (much like the wait for socket creation during application server start). If SIGINT is not acceptable by and large for rackup-spawned processes, SIGKILL could be used as well (even though it's nasty and is generally considered harmful).


Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Ruby Acceptance Testing for Web applications.

Shared Ticket Bins

People watching this ticket