Error on the export of JIRA database in PRODUCTION environment

[Maria Jesus Bernal]

Hi,

we have had during last days an error in the server where we have installed the JIRA server. The JIRA version is 7.2.1 (now unsupported) and we cannot report the error to Atlassian.

We though at the first moment that the problem was a timeout doing the export, and we increase the value from 300 to 400:

[jira@viprojira7lnx00 jira]$ grep pool-remove-abandoned-timeout dbconfig.xml

    <pool-remove-abandoned-timeout>400</pool-remove-abandoned-timeout>

..... But the error continues. The error is produced when Jira makes the internal database export, and log shows the next lines:

[jira@viprojira7lnx00 corrupted]$ cat 2020-jun-24--0100.zip.failure.txt

"La copia de seguridad al fichero '/opt/aplicaciones/jira/export/2020-jun-24--0100.zip' falló.

El fichero de copia de seguridad se ha movido a '/opt/aplicaciones/jira/export/corrupted'.

A continuación, una traza de la pila de excepción:

com.atlassian.core.AtlassianCoreException: Error exportando datos: org.ofbiz.core.entity.GenericTransactionException: Error occurred while rolling back transaction. (Violación de protocolo: [ 0, ])

        at com.atlassian.jira.service.services.export.ExportService.performBackup(ExportService.java:125)

        at com.atlassian.jira.service.services.export.ExportService.run(ExportService.java:111)

        at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)

        at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62)

        at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44)

        at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32)

        at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)

        at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)

        at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)

        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)

        at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)

        at java.lang.Thread.run(Thread.java:748)

Anybody has an idea how to solve it? We are in a critical situation without export database.

Thank you in advance.

Regards,

Maria Jesus Bernal