Shirly Radco has submitted this change and it was merged. Change subject: history: use engine-events connection that is refreshed ...................................................................... history: use engine-events connection that is refreshed If the connection to the db is lost and renewed, the connection that is currently used for updating that etl stopped does not reconnect. I replaced the connection to one that is refreshed after a connection is lost. Change-Id: I95f6c810f54913c9430b86cee57845185a257070 Bug-Url: https://bugzilla.redhat.com/1286441 Signed-off-by: Shirly Radco <sradco(a)redhat.com&gt; --- M etl_export/src/ovirt_engine_dwh/historyetl_3_6/HistoryETL.java M tos_project/process/HistoryETL_3.6.item M tos_project/process/HistoryETL_3.6.properties 3 files changed, 161 insertions(+), 9 deletions(-) Approvals: Shirly Radco: Verified; Looks good to me, approved Jenkins CI: Passed CI tests -- To view, visit https://gerrit.ovirt.org/49423 To unsubscribe, visit https://gerrit.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I95f6c810f54913c9430b86cee57845185a257070 Gerrit-PatchSet: 3 Gerrit-Project: ovirt-dwh Gerrit-Branch: master Gerrit-Owner: Shirly Radco <sradco(a)redhat.com&gt; Gerrit-Reviewer: Jenkins CI Gerrit-Reviewer: Shirly Radco <sradco(a)redhat.com&gt; Gerrit-Reviewer: Yaniv Dary <ydary(a)redhat.com&gt; Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org&gt;