| Key: |
NET-84
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Clark E. Archer
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
Operating System: Linux
Platform: PC
Operating System: Linux
Platform: PC
|
|
| Bugzilla Id: |
26296
|
| Resolution Date: |
20/Dec/06 11:02 AM
|
|
When calling TelnetClient#disconnect(), a NullPointerException is thrown because
either __input or __output is already null. After fixing my working copy of the
source, an additional NPE is thrown in SocketClient#disconnect() because the
socket variable is already null. I've patched both files to check for null of
the affected intasnce variables before calling the close() methods and will be
submitting a patch.
|
|
Description
|
When calling TelnetClient#disconnect(), a NullPointerException is thrown because
either __input or __output is already null. After fixing my working copy of the
source, an additional NPE is thrown in SocketClient#disconnect() because the
socket variable is already null. I've patched both files to check for null of
the affected intasnce variables before calling the close() methods and will be
submitting a patch. |
Show » |
| No work has yet been logged on this issue.
|
|
[net] TelnetClient#disconnect() causes NullPointerException from Linux when connected to Windows 2000 Telnet Server
