Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Long run time

Status
Not open for further replies.

clk430

Programmer
Sep 21, 2005
235
US
Sometimes when a map errors (generally a 'source not availble') launcher.txt shows a very long map run time. For expample:
System: ConcentraOutbnd
Component: FTPResendTrace
Map: E:\EC\Appint\FTPResendTrace.mmc
Start Time: Tue Jan 31 11:31:39 2006
Instance: 7
Run Time: 175.0139 seconds
Return Code: 12 - Source not available

Input 1: File: E:\EC\AppData\PGPnFTP\Concentra\Trace\RED-CN-MP168433-1-05-Jan312006_0001_3_982095292007.trigger
Input 2: File: E:\EC\AppData\PGPnFTP\Concentra\Trace\FTPPut_RED-CN-MP168433-1-05-Jan312006_0001_3_982095292007.mtr
Output 1: Sink: No Data
Output 2: Sink: No Data
Output 3: Sink: No Data
Output 4: File: E:\EC\AppData\PGPnFTP\Concentra\Trace\ResendRED-CN-MP168433-1-05-Jan312006_0001_3_982095292007.bat

What parameters do I need to change to not let it run so long and error quicker? Does it use resources staying open for so long?
 
Which file is not available? The map would normally fail as soon as the error is detected so if it's your last card that has the error, the time is used processing the preceeding cards.
Alternatively you may have a retry set on the missing file so the map would not fail until all the retries have completed.
 
How long does the map run when data is there?
How many retries have been set?
If you are trying to map the FTP trace, the file is locked while the adapter has the connection open (see IdleFTP setting in .ini and how long the map that produced the trace took to run).
It is not recommended to use adapter traceing in a production environment. Adapter tracing was designed for debugging specific issues.
Audit log should be used for error handling.
You may be triggering on the trigger file but the trace is locked.




BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
 
ah, retries are at 35X5 - not sure why it is coded so high.

The idelFTP is set to 1, however the FTP map takes about 8 seconds due to excessive apps/maps running for the hardware we have.

I did not know that about the adapter tracing being not recommmended. I learned something new. It was put in place to check for errors, then re-send the file if it appears to fail.
 
Developer trying to work around the file lock problem probably set the retries higher. Didn't fix it, but didn't take the time to get a real solution.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
 
Contracors, they come, cause problems and then get the boot faster than some of my ex-girlfriends. :)

I'll see if I can re-code this.
 
And make more $ than we do. :)



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top