Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of jsurf@gmx.de designates
 213.165.64.20 as permitted sender)
Message-ID: <43174EBF.80608@gmx.de>
Date: Thu, 01 Sep 2005 20:55:59 +0200
From: Jens Viebig <jsurf@gmx.de>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: Re: [VFS] FTPClientWrapper Broken Pipe
References: <019b01c5af0f$9a4328b0$fe78a8c0@jviebigXP>
 <43173420.8050406@ops.co.at> <4317352A.10908@elcock.org>
In-Reply-To: <4317352A.10908@elcock.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello, how do you set a timeout on the client side ?
My ftp server times out after 5 minutes, normally the connection 
restarts as expected.
My code runs inside a background service that is running 24/7 so there 
are a lot of things that can cause an 'unexpected' IOException. A 
physical network is never perfect.
Im using bea jrockit jvm that is 1.4 compatible
Im using commons-net 1.4
Yes it seems that isConnected() that is used in FTPClientWrapper does 
not do a physical test. I think i will try to replace

all catch blocks

catch (FTPConnectionClosedException e)

with

catch(IOException e)

in FTPClientWrapper

FTPConnectionClosedException is a subclass of  IOException so there  is 
no need to have two catch blocks.
Hope this will be fixed in official future releases of commons-VFS

Regards

Andrew Elcock wrote:

> What I did to get round this is to apply a timeout and after a certain 
> time I "restart" the connection. I hope this works for you to...
>
> Mario Ivankovits wrote:
>
>> Hi!
>>
>>> Caused by: java.net.SocketException: Broken pipe
>>>  
>>
>>
>> Do you know why this happens? Some sort of ftp timeout?
>>
>>>        catch (IOException ie)
>>>        {
>>>            disconnect();
>>>            throw ie;
>>>        }
>>>  
>>
>>
>> I ask as maybe we should retry the operation here too?
>>
>>
>>> Normally isConnected() should fail then, but it seems that it still 
>>> returns true
>>
>>
>> isConnected() in ftp.java is a logical operation if the connection 
>> "should be" established, not a physical check.
>> There is also a socketIsConnected which tries to check if the 
>> connections is really alive but it works only with jdk1.4 and up.
>>
>> Which jdk do you use?
>> If its 1.4 or up, which commons-net version do you use?
>>
>> ---
>> Mario
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org