Broadleaf 4.0.17-GA
Released on January 23, 2017
This is the 17th patch release for the Broadleaf Commerce 4.0 framework.
Noteworthy Updates
Optional data updates for purge improvements
This patch has an update to how Anonymous Customers and Abandoned Carts are purged. The process is now done in batches and temporarily ignores any previous customer/carts that failed to purge on previous runs.
Both the batch size and the failed purge retry period are configurable. If a value is not set there are defaults.
The following queries can be altered and run to add parameters to the purge job:
-- defaults to batch size of 50
INSERT INTO BLC\_SCHED\_JOB\_DETAIL (SCHED\_JOB\_DETAIL\_ID, SCHED\_JOB\_ID, NAME, FRIENDLY\_NAME, VALUE) VALUES (-102, -101, 'BATCH\_SIZE', 'Delete carts batch size', '50');
-- defaults to retry failed seconds equal to 48 hours
* INSERT INTO BLC\_SCHED\_JOB\_DETAIL (SCHED\_JOB\_DETAIL\_ID, SCHED\_JOB\_ID, NAME, FRIENDLY\_NAME, VALUE) VALUES (-103, -101, 'RETRY\_FAILED\_SECONDS', 'Purge cart error retry 48 hrs', '172800');
-- defaults to batch size of 50
INSERT INTO BLC\_SCHED\_JOB\_DETAIL (SCHED\_JOB\_DETAIL\_ID, SCHED\_JOB\_ID, NAME, FRIENDLY\_NAME, VALUE) VALUES (-122, -120, 'BATCH\_SIZE', 'Delete customer batch size', '50');
-- defaults to retry failed seconds equal to 48 hours
INSERT INTO BLC\_SCHED\_JOB\_DETAIL (SCHED\_JOB\_DETAIL\_ID, SCHED\_JOB\_ID, NAME, FRIENDLY\_NAME, VALUE) VALUES (-123, -120, 'RETRY\_FAILED\_SECONDS', 'Purge customer error retry 48 hrs', '172800');
An at-a-glance view of the issues that were closed in this release:
Critical Bugs(1)
- For cloning purposes created a new getter method for SkuMedia that does not reference the DefaultSku
Major Bugs(2)
- Fixed potential NPE in getCategory on OrderItem
- Admin property metadata cache does not use enough information for its cache key leading to missing properties
Enhancements(3)
- Improved purge process adding batching and periodic failure retries
- Added base IntegrationSetup class for using JUnit for IT
- Broadleaf's StringUtil.segmentInclusion is expensive
Total Resolved Issues: 6