If an exception is thrown during source control commit (export), then the local repository can be left in a dirty state, preventing any further source control operations.

An example exception report is below:

Exporting application to the repository SYSTEM SEVERE *** ERROR *** Error occurred while exporting application
org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files:
<list of files here>
at com.glide.sourcecontrol.git.GitRepository.checkout(
at com.glide.sourcecontrol.git.GitRepository.checkout(
at com.glide.sourcecontrol.worker.git.GitWorkerHelper.initRepo(
at com.glide.sourcecontrol.worker.git.GitExportApplicationWorker.exportApp(
at com.glide.sourcecontrol.worker.ExportApplicationWorker.execute(
at com.glide.sourcecontrol.SourceControlWorker.startWork(
at com.glide.worker.AbstractProgressWorker.startAndWait(
at com.glide.worker.HierarchicalProgressWorker.startAndWait(

Steps to Reproduce


This behavior happens after another problem in Source Control. Customers affected by the problem documented within KB0622532 will experience this problem afterward, so the STR for KB0622532 are a possible way to reproduce this problem.


  1. Backup any uncommitted changes by Publishing to Update Set and exporting the update set(s) to XML.
  2. Delete the relevant sys_repo_config record.
  3. Open the application and re-link it to source control.
  4. Confirm your changes are still shown in the application. If not, import them from the XML exported in step 1.
  5. Commit the changes to source control.

Related Problem: PRB916398

Seen In

There is no data to report.

Fixed In

Istanbul Patch 9
Jakarta Patch 3

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:35:55