wodftpdlx.net timeout occurred due to inactivity - WeOnlyDo Discussion board

wodftpdlx.net timeout occurred due to inactivity (General questions)

by Ryan Garaygay, Tuesday, May 20, 2008, 17:35 (6034 days ago)

I'm getting the following wodftpdlx.net timeout occurred due to inactivity.

It is sort of intermittent though, reproducible from time to time.

Using Visual Studio 2005, ASP.NET 2.0 and behaves the same for IIS and built-in Web Server (Cassini).

Looking at the event logs, this one caught my attention. I could send more details (eg. logs) through email if necessary. You could probably recognize the error but if ever it might also help if you could point me to the right direction of finding more details of the cause.

Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1334
Date: 5/20/2008
Time: 11:04:20 PM
User: N/A
Computer: MyComputerName
Description:
An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/1/Root/MyAppName

Process ID: 5180

Exception: System.NullReferenceException

Message: Object reference not set to an instance of an object.

StackTrace: at _.__._(_ , Exception )
at _._._(IAsyncResult )
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.AsyncProtocolRequest.CompleteUser()
at System.Net.Security.SslState.FinishHandshake(Exception e, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ReadFrameCallback(AsyncProtocolRequest asyncRequest)
at System.Net.AsyncProtocolRequest.CompleteRequest(Int32 result)
at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32 bytes)
at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Re: wodftpdlx.net timeout occurred due to inactivi

by Ryan Garaygay, Tuesday, May 20, 2008, 17:39 (6034 days ago) @ Ryan Garaygay

My sample code:

protected void Page_Load(object sender, EventArgs e)
{
FtpDLX ftp = new FtpDLX();
ftp.Authentication = Authentications.Password;
ftp.Blocking = true;
ftp.Encryption = EncryptionMethods.Auto;
ftp.Hostname = 127.0.0.1
ftp.Login = myUserName ;
ftp.Passive = true;
ftp.Password = myPassword ;
ftp.Protocol = Protocols.FTPS;
ftp.Timeout = 10;
ftp.TransferMode = TransferModes.Binary;
ftp.StateChangedEvent += new FtpDLX.StateChangedDelegate(ftp_StateChangedEvent);
ftp.Connect();
Response.Write( success );
}

void ftp_StateChangedEvent( object Sender, FtpStateChangedArgs Args)
{
}

Re: wodftpdlx.net timeout occurred due to inactivi

by wodDamir, Tuesday, May 20, 2008, 17:59 (6034 days ago) @ Ryan Garaygay

Hi Ryan,

Can you please try the following:

[code]public partial class _Default : System.Web.UI.Page
{
private WeOnlyDo.Client.FtpDLX ftp;
protected void Page_Load(object sender, EventArgs e)
{
ftp = new WeOnlyDo.Client.FtpDLX();
ftp.Authentication = WeOnlyDo.Client.Authentications.Password;
ftp.Blocking = true;
ftp.Encryption = WeOnlyDo.Client.EncryptionMethods.Auto;
ftp.Hostname = your_host ;
ftp.Login = your_login ;
ftp.Passive = true;
ftp.Password = your_password ;
ftp.Protocol = WeOnlyDo.Client.Protocols.FTPS;
ftp.Timeout = 10;
ftp.TransferMode = WeOnlyDo.Client.TransferModes.Binary;
ftp.StateChangedEvent += new WeOnlyDo.Client.FtpDLX.StateChangedDelegate(ftp_StateChangedEvent);
ftp.Connect();
Response.Write( success );
}

void ftp_StateChangedEvent(object Sender, WeOnlyDo.Client.FtpStateChangedArgs Args)
{
Response.Write( State changed from + ftp.StateText(Args.OldState) + TO + ftp.StateText(Args.NewState) + <br> );
}[/code]

As for the Object not set error, this is usually an issue when you try to access some membet that is not set. However, I can't tell what could cause this without seeing the whole application. Can you send us your full application source to techsupport@weonlydo.com so we can check it out?

Regards,
Damba

Re: wodftpdlx.net timeout occurred due to inactivi

by Ryan Garaygay, Tuesday, May 20, 2008, 18:15 (6034 days ago) @ wodDamir

Thanks for the response. Will try that when I encounter the issue again. Can't recreate the issue now (as mentioned not consistently reproducible). Will also email a scaled down version of the application (enough to exhibit the issue) if we still encounter it despite your recommendation above.