BIX extract from rule caused massive log file
Running BIX extract from an agent, which calls runExtract activity, increased the size of the BIX log file to approximately 80 GB. Usually the extract size is smaller than 600 KB.
Steps to Reproduce
Run BIX using an Agent calling runExtract with parameters.
A defect in Pegasystems’ code or rules:
A JDBC connection reset error resulted in BIX code printing the same error infinite times:
(internal.access.ExtractImpl) ERROR - Error on clearing the batch of table: TARGET_DB failure in Batch Execution DSRA9110E: Statement is closed.
The explanation for this behavior is as follows:
This is supported in Pega 7.1.8 (GRP-4228) and a DevTip Bug is entered to make sure such scenario is handled in next update.
0% found this useful