| Summary: | Configurable timeout for remote log import | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Samson Wai <samwai> |
| Component: | TPTP | Assignee: | Alex Nan <apnan> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | Keywords: | plan |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | closed460 | ||
|
Description
Samson Wai
Configuring the time out would normally require UI changes if we want to expose this variable to the user. Are we allowed to do UI changes in the 4.2.1 release? If not we could use a system variable that would need to be set if the user wants a different values than the default. Cannot be contained in 4.2.1 since it requires UI changes It also doesn't seem to be a defect; it is an enhancement request and more discussion and design review need to happen to have this included into a driver defer to 4.4, cannot be contained in 4.3. Samson, I have incresed the time out to 2 min. Since AS400 is the only case with such a problem and since it's not one of our supported platforms anymore, I've decided to rather increase the hard coded time out threshold then changing the UI. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |