Why doesn't the selenium grid hub free up it's port on exit?

[tom ketchup]

I've noticed that when you exit the selenium grid hub process the port still appears to be taken when you reopen if you exit under certain circumstances in windows, yielding:

[java] 2009-11-20 18:19:00.603::WARN:&nbsp; failed SocketConnector @ 0.0.0.0:4444\\ &nbsp;&nbsp;&nbsp;&nbsp; [java] java.net.BindException: Address already in use: JVM_Bind\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at java.net.PlainSocketImpl.socketBind(Native Method)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at java.net.PlainSocketImpl.bind(Unknown Source)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at java.net.ServerSocket.bind(Unknown Source)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at java.net.ServerSocket.<init>(Unknown Source)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at java.net.ServerSocket.<init>(Unknown Source)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:78)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:72)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:251)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:145)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.jetty.Server.doStart(Server.java:239)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)\\ &nbsp;&nbsp;&nbsp;&nbsp; [java]&nbsp;&nbsp;&nbsp;&nbsp; at com.thoughtworks.selenium.grid.hub.HubServer.main(HubServer.java:39)

This happens after exiting the server process with ctrl-c. Is there a way to prevent this, or even to free the port afterwards? The java process seems to have exited, but somehow it left a lock on the port?