[jira] [Resolved] (NET-304) TFTP send method having issue

["Sebb (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NET-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved NET-304.
----------------------
       Resolution: Fixed
    Fix Version/s: 3.6

TFTPClient has been rewritten for the upcoming 3.6 release; if the problem still occurs please re-open with details.

> TFTP send method having issue
> -----------------------------
>
>                 Key: NET-304
>                 URL: https://issues.apache.org/jira/browse/NET-304
>             Project: Commons Net
>          Issue Type: Bug
>          Components: TFTP
>    Affects Versions: 2.0
>            Reporter: Rahul Pujari
>            Priority: Minor
>             Fix For: 3.6
>
>
> I am using commons net 2.0 version. I have a TFTP server implemented and the scenario is below - 
> 1) Client sends TFTPWrite request.
> 2) Server sends DATA packet, client sends ACK. Server receives it (thr TFTP.receive()). 
> 3) This goes well for quite some time.  
> 4) Now server gets same ACK thrice, means some packets are not reached to client and client sends the same ACK again. 
> 5) Server also sends the old DATA packet coresponding to the ACK, using TFTP.send(). But somehow those DATA packets are not seen on the interface in the snoop log :(. So client has a timeout of say 5 secs, and closes the connection at its end indicating overall transfer failure. And I could see the DATA packet coming in the snoop log after 13-14 secs of delay :(, once TFTP.send() is invoked. 
> This does not happens always. Scenario works fine most of the times, but there are cases where it's delaying sending the packet on the i/f. And delay osberved was around 10 secs. Because of this, Client closes a connection :(.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)