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

Denis Molony updated NET-490:
-----------------------------

    Description: 
When storing a large binary file (almost 4MB) the STOR command hangs. It works 
fine with commons-net-3.2-20120413.112211-57.jar, but since changing to the 3.2 
release it no longer works. Reverting to the previous jar file works again.

It is a ravel file, file type Image, data structure Record.

I have verbose mode set, the last message shown is the '125 Storing data set 
xxx.yyy' After that, nothing more.

If I use ftp directly (without java), the same file transfers successfully.

  was:
When storing a large binary file (almost 4MB) the STOR command hangs. It works 
fine with commons-net-3.2-20120413.112211-57.jar, but since changing to the 3.2 
release it no longer works. Reverting to the previous jar file works again.

I have verbose mode set, the last message shown is the '125 Storing data set 
xxx.yyy' After that, nothing more.

If I use ftp directly (without java), the same file transfers successfully.

    
> Binary store to mainframe hangs under 3.2
> -----------------------------------------
>
>                 Key: NET-490
>                 URL: https://issues.apache.org/jira/browse/NET-490
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 3.2
>         Environment: Windows 7.
>            Reporter: Denis Molony
>
> When storing a large binary file (almost 4MB) the STOR command hangs. It 
> works fine with commons-net-3.2-20120413.112211-57.jar, but since changing to 
> the 3.2 release it no longer works. Reverting to the previous jar file works 
> again.
> It is a ravel file, file type Image, data structure Record.
> I have verbose mode set, the last message shown is the '125 Storing data set 
> xxx.yyy' After that, nothing more.
> If I use ftp directly (without java), the same file transfers successfully.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to