FTP Server
From UG
(→SOW 1) |
(→SOW 1) |
||
| Line 20: | Line 20: | ||
A processing error that occurred on both internal & client application, where the outbound FTP didn't go well and blocked all processes, it was suggested to add a mechanism to auto restart the ftp connection, to avoid having to restart entire CT2 application. | A processing error that occurred on both internal & client application, where the outbound FTP didn't go well and blocked all processes, it was suggested to add a mechanism to auto restart the ftp connection, to avoid having to restart entire CT2 application. | ||
| + | |||
| + | == SOW 1 Solution == | ||
| + | |||
| + | Mihail notes from mantis [http://ct.jaguarfreight.com/mantis/view.php?id=3289 3289] | ||
| + | |||
| + | "The process that monitors the FTP connection was added. It will automatically restart all connections if one of them failed." | ||
| + | |||
| + | === QA & UAT Notes === | ||
| + | |||
| + | As this is a background process, QA & UAT was unable to be completed 100% due to inability to reproduce a hanging FTP process. Therefore UAT was conducted by changing the "TMS update frequency(in seconds (min 10 seconds))" from 30 back to 300 to see if it fails sending. Sending passed at 300 seconds, UAT: Pass | ||
Revision as of 14:57, 16 January 2012
Contents |
Info
Parent Mantis
0001677: (CT2 Servers/Systems) ............. <parent>
Scope of this Wiki
Add mechanism for FTP automatic restart.
SOW 1
Mantis
3289: Add mechanism to make it possible to restart ftp connection without restarting application
Core Requirements
A processing error that occurred on both internal & client application, where the outbound FTP didn't go well and blocked all processes, it was suggested to add a mechanism to auto restart the ftp connection, to avoid having to restart entire CT2 application.
SOW 1 Solution
Mihail notes from mantis 3289
"The process that monitors the FTP connection was added. It will automatically restart all connections if one of them failed."
QA & UAT Notes
As this is a background process, QA & UAT was unable to be completed 100% due to inability to reproduce a hanging FTP process. Therefore UAT was conducted by changing the "TMS update frequency(in seconds (min 10 seconds))" from 30 back to 300 to see if it fails sending. Sending passed at 300 seconds, UAT: Pass
