wood burning stoves 2.0*
The moose likes Sockets and Internet Protocols and the fly likes Frequent occurence of the 426 Failure writing network stream and read Timed out exceptions seen Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Java » Sockets and Internet Protocols
Bookmark "Frequent occurence of the 426 Failure writing network stream and read Timed out exceptions seen " Watch "Frequent occurence of the 426 Failure writing network stream and read Timed out exceptions seen " New topic
Author

Frequent occurence of the 426 Failure writing network stream and read Timed out exceptions seen

ruth abraham
Greenhorn

Joined: Oct 31, 2012
Posts: 9
Hi,
Me again...with my server 1 and server 2 !
So this time again...I'm having trouble with FTP.
The scenario is as follows....
Server 1 connects via ftp to server 2 and performs an NLST, and then an MDTM and RETR on the required files on server 2.
Once the require file is successfully copied, server 1 performs a STOR to put a file on server 2.
Somehow at several points, I get the 426 error....and during some transfers, it works just fine.
I thought it might be a network issue but cant figure out whether server 1 or 2 is responsible...
Any suggestions on where I can start my search for the culprit?
I do not have access to server 2...so what can i check on my own server and ask the owners of server 2 to check on theirs?

I ran snoop for a while and got the below.
230 Login successful.
CWD /myRemotePath
250 Directory successfully changed.
PORT x,x,x,x,Y,Y
200 PORT command successful. Consider using PASV.
NLST /myRemotePath
150 Here comes the directory listing.
226 Directory send OK.
MDTM /myRemotePath/Test235.tar
213 20121012033358
MDTM /myRemotePath/Test305.tar
213 20121012040358
MDTM /myRemotePath/Test320.tar
213 20121012041858
MDTM /myRemotePath/Test335.tar
213 20121012043358
MDTM /myRemotePath/Test405.tar
213 20121012050358
MDTM /myRemotePath/Test420.tar
213 20121012051858
MDTM /myRemotePath/Test435.tar
213 20121012053358
MDTM /myRemotePath/Test505.tar
213 20121012060358
MDTM /myRemotePath/Test520.tar
213 20121012061857
MDTM /myRemotePath/Test535.tar
213 20121012063358
MDTM /myRemotePath/Test550.tar
213 20121012064858
PORT x,x,x,x,Y,Z
200 PORT command successful. Consider using PASV.
TYPE I
200 Switching to Binary mode.
RETR Test235.tar
150 Opening BINARY mode data connection for Test235.tar (10240 bytes).
226 File send OK.
PORT x,x,x,x, Y,Z
200 PORT command successful. Consider using PASV.
TYPE I
200 Switching to Binary mode.
STOR /myRemotePath/Test235.tar.temp
150 Ok to send data.
PORT x,x,x,x, Z,M
226 File receive OK.
200 PORT command successful. Consider using PASV.
PORT x,x,x,x,Z,M
200 PORT command successful. Consider using PASV.
TYPE I
200 Switching to Binary mode.
RETR Test320.tar
150 Opening BINARY mode data connection for Test320.tar (10240 bytes).
PORT x,x,x,x,Z,M
426 Failure writing network stream.
200 PORT command successful. Consider using PASV.
PORT x,x,x,x,Z,M
200 PORT command successful. Consider using PASV.
PORT x,x,x,x,Z,M
200 PORT command successful. Consider using PASV.
TYPE I
RETR Test420.tar
200 Switching to Binary mode.
PORT x,x,x,x,Z, M
150 Opening BINARY mode data connection for Test420.tar (10240 bytes).
426 Failure writing network stream.
TYPE I
200 PORT command successful. Consider using PASV.
PORT x,x,x,x,Z,M
200 Switching to Binary mode.
200 PORT command successful. Consider using PASV.
PORT x,x,x,x,Z,M
200 PORT command successful. Consider using PASV.
TYPE I
RETR Test520.tar
200 Switching to Binary mode.
PORT x,x,x,x,Z,M
150 Opening BINARY mode data connection for Test520.tar (10240 bytes).
TYPE I
RETR Test535.tar
426 Failure writing network stream.
200 PORT command successful. Consider using PASV.
200 Switching to Binary mode.
150 Opening BINARY mode data connection for Test535.tar (10240 bytes).
226 File send OK.
PORT x,x,x,x,Z,M
200 PORT command successful. Consider using PASV.
TYPE I
RETR Test550.tar
200 Switching to Binary mode.
150 Opening BINARY mode data connection for Test550.tar (10240 bytes).
226 File send OK.
PORT x,x,x,x,Z,M
200 PORT command successful. Consider using PASV.
TYPE I
STOR /myRemotePath/Test550.tar.temp
200 Switching to Binary mode.
150 Ok to send data.
QUIT
226 File receive OK.
221 Goodbye.



The error I see in the log of my application is
TRACE : 2012-08-14 13:02:52 (UTC+09:00) Error : MyChannel.putFile => Failed to put the file /myRemotePath/Test235.tar.temp
System message: java.net.SocketTimeoutException: Read timed out

Are all these caused due to the same issue?

Please help!




 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Frequent occurence of the 426 Failure writing network stream and read Timed out exceptions seen