Thread.interrupt()将不中断套接字上阻塞的线程.您可以尝试调用Thread.stop()或Thread.destroy()，但是不建议使用这些方法(在J2ME中实际上是编辑 )，由于某些原因，您可以阅读此处.正如该文章所提到的，您所遇到的***解决方案是关闭您要阻塞的套接字:

Thread.interrupt() will not interrupt a thread blocked on a socket. You can try to call Thread.stop() or Thread.destroy(), but these methods are deprecated (edit: actually, absent in J2ME) and in some cases non-functional, for reasons you can read about here. As that article mentions, the best solution in your case is to close the socket that you're blocking on:

在某些情况下，您可以使用特定于应用程序的技巧.例如，如果某个线程正在一个已知的套接字上等待，则可以关闭该套接字以使该线程立即返回.不幸的是，实际上没有任何一种技术可以正常工作.应该注意的是，在所有等待线程不响应Thread.interrupt的情况下，它也不响应Thread.stop.此类情况包括故意的拒绝服务攻击，以及thread.stop和thread.interrupt无法正常工作的I/O操作.

In some cases, you can use application specific tricks. For example, if a thread is waiting on a known socket, you can close the socket to cause the thread to return immediately. Unfortunately, there really isn't any technique that works in general. It should be noted that in all situations where a waiting thread doesn't respond to Thread.interrupt, it wouldn't respond to Thread.stop either. Such cases include deliberate denial-of-service attacks, and I/O operations for which thread.stop and thread.interrupt do not work properly.