Bugzilla – Full Text Bug Listing
| Summary: | [regression] New AC starts with no errors when configuration file is not generated | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Navid Mehregani <nmehrega> |
| Component: | TPTP | Assignee: | Igor Alelekov <igor.alelekov> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | CC: | jkubasta |
| Version: | unspecified | Keywords: | plan |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | closed460 | ||
The new AC package includes a default version of serviceconfig.xml with relative path settings, rather than an empty config like the RAC. Therefore the AC can startup just fine, but only new AC communication channels will be setup. Hence, anything relying on backwards compatibility will fail. We can delete the contents of the default config file, forcing the use of SetConfig.bat, but we also need to fix the new AC to report an error if the config file is a) non-existent or b)empty. Currently either of those cases just result in its exiting, w/o any error to indicate why. Basicly, if AC returns from configurationManager_readConfigFile() need to display an error - NOT log it since there may not be a log file. Kevin, please make sure the proper errors get displayed in all cases, a separate bugzilla will cover removing the default contents of the config. When the serviceconfig file is empty we now do not start the AC and we print a message warning the user. Verified on TPTP-4.2.0-200606060100 I'm experiencing a similar problem with the 4.4 AC. When there is no configuration file, ACServer doesn't start up, but it doesn't output any error message either. It use to generate an error message. Raising severity, since this is a regression. It seems that AC 4.5 is free from this defect. I had tested it and got the following message if config file is absent: "Error reading the Agent Controller configuration file. Please check for valid configuration". Resolving as "works for me" Please change the target to the 4.5 iteration when this Bugzilla was resolved. 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 enhancement/defect has been resolved and unverified for more than 1 year 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. |
New AC doesn't generate any errors if it's started prior to running SetConfig.bat The user can start RAServer.exe prior to running SetConfig.bat and new AC doesn't seem to complain. It seems to "start", but nothing can be profiled. The old RAC use to output the following error message when RAServer.exe was executed prior to SetConfig.bat: Couldn't load JVM library (null) Couldn't start Agent Controller Reason: Configuration file parsing failed Resolution: 1. Examine the messages in servicelog.log to determine where parsing failed. 2. Make sure you have created a valid configuration file RASERVER_HOME/config/serviceconfig.xml by running the SetConfig script.