10 minute timeout

I recently purchased the Wireless-G Broadband Router - WRT54G - 6.0. Prior to this router I had another router that worked great with my Bulletproof FTP Server software. However, now everyone seems to time out after 10 minutes of downloading. There were no timeouts like this prior to purchasing and using the new LinkSys router. Can anyone offer a solution or direct me to a thread with a solution? I have contacted LinkSys support 3 times and had help on this issue and touched every page of the options for this router. It is still not resolved.

If you have a DSL connection make sure your router is set to Keep alive for 30 seconds. If your router is idle for what ever length of time some times your ISP will time out. Your FTP software also has a time out setting so make sure that is set to 0 in most cases will set your software to no time out.
Richard Aichner (Ikester)

Similar Messages

JCO - Connection reset by peer - after 5 minute timeout

Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR       connection to partner '---removed!---:3299'
            broken
TIME        Fri Feb 11 18:08:55 201
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -6
MODULE      nixxi.cpp
LINE        4448
DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR       connection to partner '---removed!---:3299'
            broken
TIME        Fri Feb 11 18:08:55 201
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -6
MODULE      nixxi.cpp
LINE        4448
DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

LMS 3.2 Windows - 10 minute timeout while using TACACS+ Login Module

Hello,
we have changed our login module to TACACS+ (Non-ACS). All works fine when we use users which are set up in TACACS+. Using an account which does not exist (or only exists in CiscoWorks Local login module - even as fallback user) we register a timeout of 10 minutes until the login module fails the request (turned on Debugging and watching the stdout.log of tomcat). While running the backup.pl script it seems that the user "admin" tries to access the web server, but as this user is not set up in TACACS+ we have to wait 20 or more minutes until the backup starts. So, is there a way to set a timeout value for that login module?Is it known that the admin account is needed to perform the backup?
Thanks and kind regards
Allessandro

This delay is coming from your TACACS server. Can you shorten the authentication failure there? As for the user ID, check your System Identity User under Common Services > Server > Security > System Identity Setup. Make sure this use exists in the TACACS databases.

Infoview never times out (web.xml files indicate a 20 minute timeout)

I currently am using Business Objects Enterprise XIR2 w/SP3. we have an apache front end load balanced between two web servers and we are using the tomcat connector to interface with the two app servers.
Right now InfoView does not timeout not matter how long you have it open (even after 24 hrs).
I've seen several articles that mention the web.xml file and the <session-timeout> tag which all of our current files list the timeout as 20 (minutes I assume)
the file that i believe sets the timeout for infoview is the located in desktoplaunch\WEB-INF\web.xml
does anyone know if there is anohter file that i'm missing or why the timeout is not occuring.
thanks
Adam

In addition to Lionel's comment, you might want to check whether the listener section of web.xml is uncommented. Specifically, change


to

<listener>
 <listener-class>com.businessobjects.sdk.ceutils.SessionCleanupListener</listener-class>
</listener>

20 minutes timeout for full RAM/Card Encryption is...

After over 2 monhts heavy usavge, I'm quite happy with my E72 so far, except for some memory leak issues.
I did get a bit annoyed by the fact that the auto-lock feature cannot be set for more than 20 minutes. One of the resons I got the E72 was the strong RAM+Card encryption but I expected it to be a bit more flexible.
It is true that having a forced lock timeout helps protect your device (you'd forget to lock it sometimes) but there are certain occasions where I find this extremely annoying. For instance:
-When I am at home I find no need to have it locked all the time.
-When I am at work and the phone is always next to me, I find annoying that it auto-locks every 20 minutes when I'm using it as an audio player - makes you have to unlock when you want to interact
-In certain applications, it is annoying that it autolocks and you can't interact. One example is Sygic Mobile GPS software that crashes when it locks. With other software it would be annoying too as you'd be locked and unable to interact with the phone in any trip taking longer than 20 minutes.
So I have two suggestions
-Make the maximum lock delay a bit longer - for instance 60 minutes.
and/or
Give us an option similar to what you get in timed Profiles, for instance, "Stay unlocked until hh:mm" - This would be handy when you're home and well... no one is going to steal your phone/access it/lose it.

I don't mean the keyboard lock, I mean the native Symbian OS phone lock when you are using RAM and/or Card Encryption with the E72.
It is built in on the OS and you cannot set it to be over 20 minutes. If you leave your phone untouched for 20 minutes it will lock/encrypt itself.
Then you have to
1) unlock the keyboard
2) enter the unlock code to decrypt
The problem is that the auto-lock feature timer is limited to 1-20 minutes.
If you want for instance to use your phone for a GPS navigation trip and don't touch it for 20 minutes, it will lock + encrypt.... in some occasions would be nice to have a much longer timer.
I wish Nokia would tweak this in the next firmware or at least allow us to specify certain applications where it would not auto-lock at all.

Screensaver not applying with 60+ minute timeout

I am having a strange issue with a screensaver GPO. The GPO is configured to apply the screensaver after 60 minutes and is a loop back policy to override the default 15 minute screen saver lock out. The problem is the screen saver doesn't come on when the
timeout is over 60 minutes. If I change it to anything less it works as expected, the current setting is for 55 minutes and is working. I have unplugged both keyboard and mouse to make sure nothing can reset the countdown. The PC is Windows 7 Pro an is part
of a 2012 R2 domain. I have checked the registry keys, tried it on different computers all the same result.

Hi,
>> The problem is the screen saver doesn't come on when the timeout is over 60 minutes. If I change it to anything less it works as expected, the current setting is for 55 minutes
and is working.
For group policy screensaver settings are configured under User Configuration, here, I want to confirm if this phenomenon happens to all user accounts that apply the group
policy screensaver settings.
Besides, we can try to clean boot the computer to check if this phenomenon occurs.
Regarding how to perform a clean boot in Windows, the following article can be referred to for more information.
How to perform a clean boot in Windows
http://support.microsoft.com/kb/929135
TechNet Subscriber Support
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here
Best regards,
Frank Shen

Intermittent Lock Timeout Exceptions with JE 5.0.58

Hi,
During tests, the system continues to experience Lock Timeout problems from time to time, even with the latest version 5.0.58. The collection contains data which is typically removed shortly after inserted, so records usually have a short lifetime. There are multiple writer threads and 1 delete / reader thread.
Any tips? Note the timeout is already a healthy 3 minutes long, so I don't think that's the problem. Stack trace and details below.
Maybe the best thing to do is to reduce the lock timeout in order to not block the data pipeline, if a simple retry fixes it?
Thanks,
Karl
ERROR@00:08:03 com.sleepycat.je.LockTimeoutException: (JE 5.0.58) Lock expired. Locker 879535510 -1_dbreader--Thread-5_ThreadLocker: waited for lock on database=persist#ListenerStore#com.procon.data.msg.local.BerkeleyDBMessage LockAddr:
892328566 LSN=0xffffffff/0x5882af type=READ grant=WAIT_NEW timeoutMillis=180000 startTime=1344323103818 endTime=1344323283850
Owners: [<LockInfo locker="1242902705 -1_CAL-dbwriter--Thread-18_ThreadLocker" type="WRITE"/>]
Waiters: []
com.sleepycat.je.txn.LockManager.newLockTimeoutException(LockManager.java:664)
com.sleepycat.je.txn.LockManager.makeTimeoutMsgInternal(LockManager.java:623)
com.sleepycat.je.txn.SyncedLockManager.makeTimeoutMsg(SyncedLockManager.java:97)
com.sleepycat.je.txn.LockManager.lockInternal(LockManager.java:390)
com.sleepycat.je.txn.LockManager.lock(LockManager.java:276)
com.sleepycat.je.txn.BasicLocker.lockInternal(BasicLocker.java:118)
com.sleepycat.je.txn.Locker.lock(Locker.java:443)
com.sleepycat.je.dbi.CursorImpl.lockLN(CursorImpl.java:2589)
com.sleepycat.je.dbi.CursorImpl.lockLN(CursorImpl.java:2390)
com.sleepycat.je.dbi.CursorImpl.searchAndPosition(CursorImpl.java:2118)
com.sleepycat.je.Cursor.searchInternal(Cursor.java:2666)
com.sleepycat.je.Cursor.searchAllowPhantoms(Cursor.java:2576)
com.sleepycat.je.Cursor.searchNoDups(Cursor.java:2430)
com.sleepycat.je.Cursor.search(Cursor.java:2397)
com.sleepycat.je.Cursor.readPrimaryAfterGet(Cursor.java:3703)
com.sleepycat.je.SecondaryCursor.readPrimaryAfterGet(SecondaryCursor.java:1470)
com.sleepycat.je.SecondaryCursor.retrieveNext(SecondaryCursor.java:1448)
com.sleepycat.je.SecondaryCursor.getNext(SecondaryCursor.java:560)
com.sleepycat.util.keyrange.RangeCursor.doGetNext(RangeCursor.java:897)
com.sleepycat.util.keyrange.RangeCursor.getNext(RangeCursor.java:451)
com.sleepycat.persist.BasicCursor.next(BasicCursor.java:80)
com.sleepycat.persist.BasicIterator.hasNext(BasicIterator.java:49)
com.procon.data.msg.local.BerkeleyDBMessageStore.queryMessages(BerkeleyDBMessageStore.java:498)
com.procon.listener.DatabaseReader.runMain(DatabaseReader.java:161)
com.procon.base.BasicRunnable.run(BasicRunnable.java:274)
java.lang.Thread.run(Thread.java:662)

Karl,
With a 3 minute timeout, you may have a true deadlock (which are sometimes expected) or a bug in your app where you neglect to close a cursor or close a transaction. Increasing the lock timeout is usually not the solution, but the first step is to diagnose what is causing it, and you haven't given us enough information to do that. You haven't said what isolation modes you're using, what transactions are active, how many records are involved in each transactions, etc.
I suggest that you read:
http://docs.oracle.com/cd/E17277_02/html/TransactionGettingStarted/index.html
in particular the Concurrency chapter.
Also see:
http://www.oracle.com/technetwork/database/berkeleydb/je-faq-096044.html#HowdoIdebugalocktimeout
for how to get more information about this particular lock conflict.
--mark

SSRS Integrated mode failes (timeout) when executing lengthy reports.

Hi All,
I have SSRS 2008 R2 running in integrated mode with SharePoint 2010 foundation. The SharePoint farm and SSRS are both configured for Kerberos authentication. Both SSRS and SharePoint are working well. The vast majority of reports
compile in less than 30 seconds, users are generally happy.
Except, I have a couple of reports which take a long time to execute on the SQL side, I cant change this, that's just how it has to be. The simplest of the reports to explain is a report, with 1 parameter with four values, which performs
up to four actions on the SQL Server and then returns around two dozen rows of the result, typically the entire process completes in around 10 minutes. If I run this report via the ssrs /reportserver WFE the report always completes, results are presented
on screen, no issues whatsoever. When I run the same report from within SharePoint, its a different story, the report will complete only if I select just one of the four parameter actions, resulting in the total report execution time of
around 4 minutes, However when running the report with all four parameters selected, the loading spinner appears, then after 6 minutes, disappears entirely. The page returns to the parameter selection, no results are presented.
Having checked all the SSRS log files and ExecutionLogStorage table, they suggest that the report carries on building in the background, and then completed roughly 10 minutes after starting.
So my conclusion is that something in SharePoint does not like the extended duration of the report execution. But what is it, What triggers the 6 minute timeout?
Any help much appreciated.
Regards
Dan

Hi danbridgland,
According to your description, there are a couple of reports in SSRS Sharepoint integrated mode. The query takes a long time to execute in SQL Server. When you run the report via Sharepoint WFE, the report works fine. When you run the report in Sharepoint
Application, the report will be displayed if you select one parameter value, if four values of the parameters are selected, the report disappears after 6 minutes’ loading.
In Native mode, SSRS uses a default timeout of 9000 seconds. In SharePoint integrated mode the timeout is reduced to 120 seconds. The timeout in SharePoint is actually related to the fact that reports are rendered using the http runtime. Any operation that
is launched from within SharePoint using the httpRuntime object has to complete within the timeout parameters. In this case, we can directly editing timeout in web.config by following steps:
Locate web.config for the SharePoint site you have configured for SSRS integration (default location: C:\inetpub\wwwroot\wss\VirtualDirectories\80).
Open the file in an XML or text editor.
Navigate to httpRuntime element, inside the tag, add executionTimeout="9000".
In addition, in SharePoint integrated mode, reports typically run slower than when the same reports run in native mode. One main cause of this latency can be attributed to SharePoint object model calls that are made. For detail information, please refer
to the following document:
http://support.microsoft.com/kb/2216504
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu

Session timeout Hyperion Planning 4.0.1

Hello, on our clients the planning-session times out after 3 minutes. I have set the session timeout setting for Apache Tomcat 4.1 in the File web.xml to the number 60, but the session already times out after 3 minutes. Can you help me? Best regards, Rainer

This could be a setting on the network/intranet/internet at the client. Had a similar problem at one of our clients and it was down to a 3 minute timeout on any request over the intranet. Worth a check with the IT department on it. Hope this helps. Andy King www.analitica.co.uk

"Page not found" error after 5 minutes of see "processing" on the screen

We are using WebLogic 8.1 server and also the WebLogic proxy as our front end. When a user runs a process that takes over 5 minutes using the Proxy URL they receive an IE "Page not found" error after 5 minutes of seeing "processing" on the screen. If they run it on none Proxy URL (directly on WebLogic server) it works fine.
We have looked into the WLIOTimeoutSecs parameter and set in the web.xml for both the HttpClusterServlet and HttpProxyServlet, but this had no affect.
Is there another timeout that controls this 5 minute timeout? It seems if one uses Apache and sets the WLIOTimeoutSecs parameter to a higher number than 300 seconds there is not an issue.
Did this parameter get omitted for the WebLogic Proxy and if so, what does one use?
Thanks,
Jim

Hello George,
Thank you for the quick reply. I will surely try the option suggested by you.
But what i was thinking is that as this is not a Connection Time Out (500) error, instead its a Page Not Found error, it would be Session-Timeout and not Connection Time-Out.
Maybe I should be looking at:
SESSION-TIMEOUT due to kernel:
Kernel parameter: rdisp/gui_auto_logout
Kernel parameter: rdisp/plugin_auto_logout
as per the SAP OSS Note: 705013
But again, I think this Note is pointing to the SICF service and IAC type of iView and not SAP Transaction type iView. Please advice.
Thanks,
Gaurav
Edited by: Gaurav Shah on Dec 4, 2008 9:37 PM
Edited by: Gaurav Shah on Dec 4, 2008 9:42 PM

Webi Timeout (Launchpad or Rich Client)

Dear experts,
I am not being able to increase timeout. I am on SBOP 4.0 SP8.1.
I followed all the guidelines from
http://help.sap.com/businessobject/product_guides/boexir4/en/xi4sp8_aa_admin_en.pdf
and
http://vynesolutions.wordpress.com/2013/04/19/configuring-business-objects-4-0-session-timeout-settings/
restarted BO servers / Tomcat.
Nothing changed. It still gives me a 20 minutes timeout instead of hte desired 45 minutes.
Thanks in advance for your help,
Kind regards,
André Oliveira

Hi Kishore,
Infoview does not support any local data source for creating the report. Also refresh from personal local data providers is currently supported with WebI Rich Client and Desk-I.
You need to create an universe on the spread sheet for getting the report to refresh in the infoview.
Also if you search, you will find a lot of threads are running on the same topic.
Regards,
Rohit

Session timeout in OBIEE11g brings Oracle annoyances to new level.

There is not a single place you can configure that sixteen-minute timeout from bothering the crap out of your users. There are lots of timeout settings in various configuration files, but none of them control this particular annoyance. I just rolled out a new instance to our Finance department, and they hate it already. How could this stupid setting not be configurable?

Hello Venkat,
I have implemented the same in my Application(OBIEE).Check it may helpful for you.
Sasi Nagireddy: HOW TO CONFIGURE SESSION TIMEOUT IN OBIEE-11G..
Thanks,
Sasi Nagireddy..

Query timeouts in ABAP

Hello all,
We are running Business Objects 4.0 SP2 and have some users running queries to our ERP system. They say they are running them in the background, but they are still timing out after 10 minutes with an ST22 stating they are exceeding the 600 second timeout limit.
"The program "%_T008C0" has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated."
Is there something they can do differently or an extra selection they need to make to avoid these query timeouts? I do not want to extend the timeout using profile param "rdisp/max_wprun_time" in a production system...
I am looking for another solution besides telling them to query less data.
Any help would be appreciated.
Thanks.

Hello Aman,
We adjusted param "rdisp/max_wprun_time" to extend timeouts across the system. However, eventually the functional team worked to re-write the query so it would not run beyond the standard 10 minute timeout.

Reasons why a query timeout would fail to cancel the query

Let's say I am running an SQL query via JDBC and then I hit the query timeout I had set on the session. 9 times out of 10 Oracle complies and I get hit with a ORA-01013 user canceled query, as I would expect. But sometimes, it seems the database just doesn't abide by my request. Is that possible? I know it's a "request", so is it truly a request and not a demand? :) Can the database choose to not obey the request or could it be in some state where it cannot comply even if it wanted to?

Oracle Enterprise Edition 10.2.0.3.0. The application is my application, a Java application that uses Hibernate sessions to communicate with the database in read only mode. I have a query timeout set on the Query object for a particular query. On my instance (Oracle 11g) i never see the occurrence. Oracle always cancels the query with an ORA-01013 right at exactly the 3 minute timeout. On their Oracle 10 instance, we see examples of the query surviving the cancel request and running as long as 10 minutes.

Deferred Message Timeout

The Default is 4 days for a Deferred Message Timeout in GroupWise. My questions are: Is this an RFC standard? I have been asked to shorten, Have other GroupWise shops shortened the Deferred Message Timeout?
Thanks

On 4/6/2012 7:30 AM, Kirk White wrote:
> The Default is 4 days for a Deferred Message Timeout in GroupWise. My
> questions are: Is this an RFC standard? I have been asked to shorten,
> Have other GroupWise shops shortened the Deferred Message Timeout?
> Thanks
It's mostly recommendations in RFC 2821
but they recommend 4-5 days
4.5.4.1. Sending Strategy
The general model for an SMTP client is one or more processes that
periodically attempt to transmit outgoing mail. In a typical system, the
program that composes a message has some method for requesting immediate
attention for a new piece of outgoing mail, while mail that cannot be
transmitted immediately MUST be queued and periodically retried by the
sender. A mail queue entry will include not only the message itself but
also the envelope information.
The sender MUST delay retrying a particular destination after one
attempt has failed. In general, the retry interval SHOULD be at least 30
minutes; however, more sophisticated and variable strategies will be
beneficial when the SMTP client can determine the reason for non-delivery.
Retries continue until the message is transmitted or the sender gives
up; the give-up time generally needs to be at least 4-5 days. The
parameters to the retry algorithm MUST be configurable.
A client SHOULD keep a list of hosts it cannot reach and corresponding
connection timeouts, rather than just retrying queued mail items.
Experience suggests that failures are typically transient (the target
system or its connection has crashed), favoring a policy of two
connection attempts in the first hour the message is in the queue, and
then backing off to one every two or three hours.
The SMTP client can shorten the queuing delay in cooperation with the
SMTP server. For example, if mail is received from a particular address,
it is likely that mail queued for that host can now be sent. Application
of this principle may, in many cases, eliminate the requirement for an
explicit "send queues now" function such as ETRN [9].
The strategy may be further modified as a result of multiple addresses
per host (see below) to optimize delivery time vs. resource usage.
An SMTP client may have a large queue of messages for each unavailable
destination host. If all of these messages were retried in every retry
cycle, there would be excessive Internet overhead and the sending system
would be blocked for a long period. Note that an SMTP client can
generally determine that a delivery attempt has failed only after a
timeout of several minutes and even a one-minute timeout per connection
will result in a very large delay if retries are repeated for dozens, or
even hundreds, of queued messages to the same host.
At the same time, SMTP clients SHOULD use great care in caching negative
responses from servers. In an extreme case, if EHLO is issued multiple
times during the same SMTP connection, different answers may be returned
by the server. More significantly, 5yz responses to the MAIL command
MUST NOT be cached.
When a mail message is to be delivered to multiple recipients, and the
SMTP server to which a copy of the message is to be sent is the same for
multiple recipients, then only one copy of the message SHOULD be
transmitted. That is, the SMTP client SHOULD use the command sequence:
MAIL, RCPT, RCPT,... RCPT, DATA instead of the sequence: MAIL, RCPT,
DATA, ..., MAIL, RCPT, DATA. However, if there are very many addresses,
a limit on the number of RCPT commands per MAIL command MAY be imposed.
Implementation of this efficiency feature is strongly encouraged.
Similarly, to achieve timely delivery, the SMTP client MAY support
multiple concurrent outgoing mail transactions. However, some limit may
be appropriate to protect the host from devoting all its resources to mail.
===========

10 minute timeout

Similar Messages

Maybe you are looking for