RE: Increasing LEI activity runtime before timeout Daniel W Heichel 7.Aug.12 03:29 AM a Web browser LEI LEI - 8.0All Platforms
The field you are asking about is called "Maximum duration of activities". It's a global setting, found in the decsadm.nsf's Configuration view -> Server document.
However, I don't believe that this setting is the problem. What that setting does is, obviously, to kill activities that run beyond a certain length. However, the message you will usually see if this comes into play is:
Process c:\Lotus\Domino\nleiact.exe (xxx/yyy) has terminated abnormally
What you are seeing is completely different. "Network Operation did not complete in a reasonable amount of time" indicates that the activity was cut off by the network, not by LEI. Something in your environment may have its own "maximum duration", and is cutting off the LEI activities.
Resolving the network issue is the first and most obvious solution. You can also maximize the efficiency of the activity via the following means (if possible):
- Don't enforce form design in the Notes connector, as this forces the activity to perform Notes field/form operations as part of the activity execution
- Consider what document options (notes-side only), formulas, and other extra activity is necessary in both connectors
- Turn off logging in the DB2 Connector
- In the Direct Transfer activity, increase the value of "Number of Records to Transfer Concurrently" to increase performance. Anywhere from 20-100 is common.
If you are simply working with a tremendous amount of data, of such volume that the job cannot be streamlined to fit, you may want to consider splitting this activity up into two or more smaller activities. Each can be set as a dependant of the last so that they fire sequentially, and this often gets them small enough to run individually.
Return to top
. . RE: Increasing LEI activity runtime... (Daniel W Heiche... 7.Aug.12)
Print this page
