This is the code that performs the interrupt():

   server.interrupt();         
   synchronized(sock) {
      try {
         sock.close();
      }
      catch(Exception e) {
         System.err.println("Error Closing Socket");
      }
   }

This is the code that it's interrupting:

   try {
      synchronized(sock) {
         while(true) {
            if(!gateways.empty())
                customer  = (HTTPGateway)gateways.remove();
            else {
                customer  = new HTTPGateway(this, kernel, props, keepalive, linger, timeout);
                customer .queueConnection();
            }
             customer .init(sock.accept());
         }
      }
   }
   catch(Exception e) {
      System.err.println("Service Interrupted");
   }

The interrupt should always be happening in the sock.accept()
statement but it doesn't. 
======================================================================

None That I Can Think Of
======================================================================

Contingent upon the implementation of asynchronous I/O.
  xxxxx@xxxxx   2000-01-13

I am closing this bug as a duplicate of 4154947.
  xxxxx@xxxxx   2000-12-21

No blocking I/O can be interrupted in JDK 1.1.x on any platform.

David Holmes' comment is incorrect.  I have code
which interrupts blocking I/O under Solaris 
without a problem.
This bug is actually a duplicate of 4154947.

do sock.setSoTimeout(1000) for the ServerSocket, and check isInterrupted on
each loop.
NOTE: this causes an overhead (check isInterrupted() every 1000ms), but only
when the server is IDLE. if the server is working, the overhead is minimal
(calling isInterrupted() )