i am using jetty as an embedded server where i add contexts (or Handlers) to jetty server for different web applications or servlets.
when i stop the jetty server with some Http connections still remaining by the Http Clients and restart it immediately without any delay, it start getting 404 errors once i try hitting the URIs.
earlier i thought, it could be due to war files not getting properly exploded, but that is not the case.
it seems if there is small delay between start and stop, jetty corrupts the contexts and hence the error.
also to observe is the case, where new URIs added are not reflected in the restarted server.
i am getting this issue in jetty 6.1.8
