[ https://jira.jboss.org/jira/browse/JBAS-5791?page=com.atlassian.jira.plug... ] Takayoshi Kimura updated JBAS-5791: ----------------------------------- Description: This is similar to JBAS-4525, but in ReadTask. The in.readByte() call in ReadTask won't be interrupted when the thread is interrupted. When this happened the connection.close() call in client won't return until socket timeout, 2 min by default. Since it's blocking socket, we can't use short timeout approach applied for WriteTask. The only way to interrupt ReadTask is to call Socket.close() or close() on InputStream underlying socket. was: This is similar to JBPAPP-685, but in ReadTask. The in.readByte() call in ReadTask won't be interrupted when the thread is interrupted. When this happened the connection.close() call in client won't return until socket timeout, 2 min by default. Since it's blocking socket, we can't use short timeout approach applied for WriteTask. The only way to interrupt ReadTask is to call Socket.close() or close() on InputStream underlying socket. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira