Summary | Fix for parasoft log parsing where usage is carried over the next day |
Platform | Windows |
Category | bugfix |
Valid for | 6.2.x, 6.3.x, 6.4.x |
Requires | |
Server Required Patch/es | |
Supersedes | 1252, 1199 |
Superseded by | |
Affects | Client: License Analyzer |
Last Updated | April 6, 2016 |
General Description: Modifies the processing of Timeout for ParasoftEventsParser and added reporting of 0 license usage. It will now compare records to the latest record's start time instead of current machine time. Detailed Description: When there are hanging license checkouts in the logfile, those checkouts will always be recorded by the parser causing erroneous report. Previously,a fix was added by introducing a "timeout" configuration but it uses the current machine's time vs. the log event's time resulting to a problem regarding the basis on how to remove those hanging license checkouts. It should use the recent log file event's time vs. the log event's time. Note: The user is required to modify matchobjects-parasoft.oconf and put their desired max available license before enabling the job. root.matchobjects.post-processing.data-process4.value=licenses=<number of max available license> In this patch revision, only the needed configurations will be modified instead of overwriting the whole configuration file. This way, user modifications will be preserve.
Adds support on the collection of Parasoft license data through parasoft log files. Note that this patch is in ALPHA status. We would appreciate to get feedback from the end-user regarding this feature. To turn this on we have to configure: - Configuration\Components\logfilecollector-parasoft.xml, set logfilecollector.source.dir to point to the location of parasoft log files. - Configuration\scheduler\client-parser-parasoft.oconf, turn on scheduler.jobs.logfilecollection-parasoft.general.active to start collection of log file data. Restart the client service.
Adds support for collection of Parasoft license data through parasoft log files. Note that this patch is in ALPHA status. We would appreciate to get feedback from the end-user regarding this feature. To turn this on we have to configure - Configuration\Components\logfilecollector-parasoft.xml, set logfilecollector.source.dir to point to the location of parasoft log files. - Configuration\scheduler\client-parser-parasoft.oconf, turn on scheduler.jobs.logfilecollection-parasoft.general.active to start collection of log file data. And restart the client service
Unpack the zip file anywhere on the machine to patch. Run install.exe to start installation. Once the patch has been installed, you may delete the unpacked directory. NOTE: The patch must be installed by a user with administrator rights.
No corresponding Patches available.