commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Savarese (JIRA)" <>
Subject [jira] Commented: (NET-146) wrong handling of timeouts
Date Tue, 19 Dec 2006 21:31:22 GMT
    [ ] 
Daniel Savarese commented on NET-146:

After reviewing the old bugzilla issue, I think the problem is that the telnet protocol implementation
for the control connection always sits in a read waiting for events (and that read is timing
out).  If that read were started only after the data transfer completed, it wouldn't time
out.  If that's the case, then, yes, that would be a bug and that's why disabling the reader
thread works around the problem. Rory's changes for 2.0 won't have the problem because it
doesn't use TelnetClient.

> wrong handling of timeouts
> --------------------------
>                 Key: NET-146
>                 URL:
>             Project: Commons Net
>          Issue Type: Bug
>    Affects Versions: 1.4 Final
>         Environment: linux 2.6, java 1.5.0_08 (but most probably any environment)
>            Reporter: Koloom
> If you set a timeout on the control connection and then make a data transfer (upload,
download) which takes longer than that timeout, the client throws the following exception.
It seems like the client tries to read something from the control connection while the data
transfer is in progress and then it just throws an exception. It makes the application think
that the transfer failed even though it succeeded.
> aused by: Read timed out
>         at Method)
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message