This is a fallout from
DERBY-3304 https://issues.apache.org/jira/browse/DERBY-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566169#action_12566169 (Dan's comment "For the update conglomerate clearing, I think that's code that is in the wrong location, probably should be in the result set that set that field. That's probably a separate issue.")
At the time of commit processing, GenericLangaugeConnectionContext.endTransactionActivationHandling does following
At the time of rollback processing, BaseActivation.reset() does following
updateHeapCC = null;
Seems like the code for clearing conglomerate should be in a different place. I haven't done research myself but wanted to log it as a jira entry so we do not forget about it.