- Article Type: General
- Product: Primo
- Product Version: 2
A pipe that stops at the dedup_merge stage with a java heap space error can be caused when during a publishing process the same record appears twice in the same pipe, once as update and the second time as deleted.
The problematic scenario is when an previously updated dedup member record is marked for deletion. This causes the record to receive a wrong type causing the out of memory because of a -1 value being selected.
In this case the pipe is stopped at stage dedup_merge with a java heap space error.
This has been fixed in SP 2.1.6, RN 5698.
- Article last edited: 10/8/2013