Summary
A user is not able to capture a baseline. The user receives an error message during the baseline verification process that indicates that the feature “capture_baseline” has exceeded size limit fuse for some entity.
Error
A user is not able to capture a baseline. The user receives an error message during the baseline verification process that indicates that the feature “capture_baseline” has exceeded size limit fuse for some entity.
Cause
When the user captures a baseline, there are limitations related to the closure size for each entity.
Fix
Add 2 site parameters in the Server Configuration tab (in Site Administrator) –
1) PARAM NAME:LIBRARY_FUSE
VALUE:300000
2) PARAM NAME:CLOSURE_ROWS_FUSE_FACTOR_PCT
VALUE:300000
Parameter Details:
LIBRARY_FUSE:
The parameter value indicates the base number for calculating the maximum number of entities for a library, in order to maintain optimal performance. By default, the value is 2500.
Calculation is performed as follows:
• Maximum number of tests in a library = LIBRARY_FUSE * 1 (2500 by default)
• Maximum number of resources in a library = LIBRARY_FUSE * 0.25 (625 by default)
• Maximum number of business components in a library = LIBRARY_FUSE * 0.25 (625 by default)
A validation of this value is performed when you create baselines, import libraries, or synchronize libraries.
CLOSURE_ROWS_FUSE_FACTOR_PCT:
The parameter value is used to adjust the limitation on the number of rows of each table (Entity) allowed in a closure for all features (such as baseline, VC, COPY/PASTE). It’s a percentage. The default value is 100, which means 100% of original defined limitation on the number of rows for each entity. Setting this value to 300000, for example, means 3000 times of original limitation.