EldoS | Feel safer!

Software components for data protection, secure storage and transfer

AS2 sender timout exception. What do you suggest?

Also by EldoS: CallbackFilter
A component to monitor and control disk activity, track file and directory operations (create, read, write, rename etc.), alter file data, encrypt files, create virtual files.
#29095
Posted: 04/02/2014 14:09:57
by Ivan Demkovitch (Standard support level)
Joined: 11/10/2013
Posts: 23

With one specific partner (server) we have following exception once in a while (when they have "issues")

Code
Connection Timeout
at SBSimpleSSL.TElCustomSimpleSSLClient.DoMessageLoop(Boolean NoPeek)
   at SBHTTPSClient.TElHTTPSClient.PerformExchange()
   at SBHTTPSClient.TElHTTPSClient.PerformRequest(Int32 Method, String URL)
   at SBHTTPSClient.TElHTTPSClient.Post(String URL, Stream Content, Boolean CloseStream)
   at SBAS2.TElAS2Client.Send(String URL, Stream Message, Stream Receipt)


I wonder what should we do in this case? Should we increase timeout value (and how?)

What is default value?
#29096
Posted: 04/02/2014 14:15:12
by Eugene Mayevski (EldoS Corp.)

Yes, timeout can be set via TElAS2Client.Socket.Timeout property. the value is in milliseconds (i.e. 60000 is 60 seconds).


Sincerely yours
Eugene Mayevski
#29097
Posted: 04/02/2014 14:25:44
by Ivan Demkovitch (Standard support level)
Joined: 11/10/2013
Posts: 23

According to documentation default is 60 seconds. Is that a practical value? I'm just curious because usually I see servers responding within 5 seconds.

I wonder if we should lower it to like 15 seconds.
#29098
Posted: 04/02/2014 14:32:44
by Eugene Mayevski (EldoS Corp.)

In most situations 15 seconds is enough. If your partner has some issues, increasing the value to anything above two minutes probably doesn't make much sense as the server might be just down (unavailable) for 5-10 minutes or more. I think you should handle the exception and try to resend the message several times with increased intervals (eg. wait 1 minute after 1st attempt, 5 minutes after second attempt, 15 minutes after third attempt, then give up).


Sincerely yours
Eugene Mayevski
#29099
Posted: 04/02/2014 14:34:21
by Ivan Demkovitch (Standard support level)
Joined: 11/10/2013
Posts: 23

We already have retry logic built in, so it is handled. I think we going to lower timeout to reduce number of potential waits/sockets.
#29422
Posted: 05/12/2014 04:28:59
by Bernard L. (Premium support level)
Joined: 12/18/2012
Posts: 14

Hi,

The TElAS2Client.Socket.Timeout property is not in the online documentation, is that possible?

https://www.eldos.com/documentation/sbb/documentation/ref_cl_as2client.html

But, be that as it may, we use TElAS2Client.WebTunnel, so is there a property TElAS2Client.WebTunnel.Timeout or can we set TElAS2Client.Socket.Timeout before starting the webtunnel? This is not something I can figure based on the documentation, honestly.

We have the impression that the default is something like 10 or 15 seconds by the way - but I can't find the default timeout setting either. If you can give a quick response to these few questions (especially how to set the timeout value for the webtunnel) that would be great. Thanks.
#29423
Posted: 05/12/2014 04:39:22
by Vsevolod Ievgiienko (EldoS Corp.)

Quote
The TElAS2Client.Socket.Timeout property is not in the online documentation, is that possible?

Indeed its missing. We'll add it.

TElAS2Client.Socket.Timeout will set the timeout even if connection is performed via web tunnels.
#29424
Posted: 05/12/2014 04:54:42
by Bernard L. (Premium support level)
Joined: 12/18/2012
Posts: 14

"TElAS2Client.Socket.Timeout will set the timeout even if connection is performed via web tunnels."

Great, thank you.

PS. I'm still missing the information about the default timeout value (I don't strictly need it but it would have been useful to prove to our customer why and at what point exactly the timeout occurred).
#29425
Posted: 05/12/2014 05:04:08
by Vsevolod Ievgiienko (EldoS Corp.)

Timeout value is set to 60 seconds by default.
Also by EldoS: Rethync
The cross-platform framework that simplifies synchronizing data between mobile and desktop applications and servers and cloud storages

Reply

Statistics

Topic viewed 2902 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!