| Summary: | Throw more meaningful IOException when trying to read a packet from a closed socket | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> | ||||
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Simon Kaegi <simon_kaegi> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | thatnitind | ||||
| Version: | 3.2 | ||||||
| Target Milestone: | 3.3 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
The patch check for socket closure and throws an IOException that the socket has been closed. applied to HEAD |
Created attachment 175839 [details] proposed fix code from HEAD If for some reason the socket gets closed while the PacketRecieveManager is about to read from it you currently get a cryptic "Invalid content length: XX" IOException. We should check for socket closure before blindly trying to read from it, and throw a more meaningful exception.