We are seeing an issue with the handling of TCP connection close when
using SOAP over HTTPS on 1.4.2. We are the client send SOAP requests to
a server running on Cisco CallManager software. In our scenario, the
server closes the TCP connection after sending a response of a request.

Client Server
  | Request1 |
  | ------------------> |
  | Response |
  | <------------------ |
  | FIN |
  | <------------------ |
  | ACK |
  | ------------------> |
  | Request2 |
  | ------------------> |
  | RST |
  | <------------------ |
  | |


As illustrated above, after the server sends FIN to client, if there is
request coming, the client will still send them, but the server would
reset the connection as it's already indecated to disconnect. The issue
happens afterwards, in the current implementation of 1.4.2, the request2
fails with an IOException saying "Unexpected end of file".

We tried this on 1.4.2 over HTTP and also on J2SE 1.5 over HTTPS, and we
observed different behavior. After the RST, the client would create a
new TCP connection and resend the same request2 again, and the request
suceed eventually.

Client Server
  | Request1 |
  | ------------------> |
  | Response |
  | <------------------ |
  | FIN |
  | <------------------ |
  | ACK |
  | ------------------> |
  | Request2 |
  | ------------------> |
  | RST |
  | <------------------ |
  | |
  | New conn. handshake |
  | <------------------> |
  | Request2 |
  | ------------------> |
  | Response |
  | <------------------ |
  | FIN |
  | <------------------ |
  | ACK |
  | ------------------> |
  | ... |


Based on the exception we received for 1.4.2 over HTTPS, we were not
able to clearly distinguish this particular situation with other
communication failures. It created a great deal of difficulties in error
handling. Also, adding special handling would greatly impact system
perfomance.