CMJ- Troubleshooting generic transaction exception during snapshot deployment

Problem

When deploying snapshots using Configuration Manager for Jira (CMJ) in Data Center, customers may encounter the ‘GenericTransactionException: Error occured while starting transaction’.

5ea3ee67-3048-4a8b-a3dd-ab0d743b0b2e-20250903-160019.png

Solution

This could be due to a significant problem with the database connection during the deployment process.
In the Atlassian logs, errors such as Connection reset, There was an error getting a DBCP datasource, and Database 'xxxxx' on server 'yyyyy' is not currently available indicate a database connection issue. The following error logs are examples.

2023-09-07 03:07:13,819-0700 NodeReindexServiceThread:thread-0 ERROR      [NoModule] There was an error getting a DBCP datasource.
java.lang.RuntimeException: Unable to obtain a connection from the underlying connection pool
	at org.ofbiz.core.entity.jdbc.interceptors.connection.ConnectionTracker.trackConnection(ConnectionTracker.java:52)
	at org.ofbiz.core.entity.transaction.DBCPConnectionFactory.trackConnection(DBCPConnectionFactory.java:283)
	at org.ofbiz.core.entity.transaction.DBCPConnectionFactory.getConnection(DBCPConnectionFactory.java:80)
	at org.ofbiz.core.entity.ConnectionFactory.tryGenericConnectionSources(ConnectionFactory.java:69)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Database 'jiradb-stg-aug-30-2023' on server 'm-usw2-sqlp-stg' is not currently available.  Please retry the connection later.  If the problem persists, contact customer support, and provide them the session tracing ID of 'A8802E5B-6220-40CB-A381-4E9B6A6F8735'. ClientConnectionId:d49e3b5a-921e-4efd-a42e-f6c7764dfea9
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
	at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:283)
	at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:129)
...

2023-09-07 02:42:59,871-0700 http-nio-8080-exec-48 url: /rest/configuration-manager/1.0/deployment/2; user: ktalapaneni ERROR ktalapaneni 162x586705x2 3cpyc1 216.228.127.129:57458,10.13.230.40 /rest/configuration-manager/1.0/deployment/2 [c.b.j.r.impl.rest.AbstractResource] java.lang.reflect.UndeclaredThrowableException
java.util.concurrent.ExecutionException: java.lang.reflect.UndeclaredThrowableException
	at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
	at com.botronsoft.jira.rollout.impl.jobs.AbstractAsyncOperation.getResult(AbstractAsyncOperation.java:61)
	at com.botronsoft.jira.rollout.rest.internal.snapshot.DeploymentResource.createResponse(DeploymentResource.java:876)
	at com.botronsoft.jira.rollout.rest.internal.snapshot.DeploymentResource.getDeploymentOperationResult(DeploymentResource.java:570)
    ...
Caused by: java.lang.reflect.UndeclaredThrowableException
	at com.sun.proxy.$Proxy6500.save(Unknown Source)
	at com.botronsoft.jira.rollout.impl.audit.AuditServiceImpl.updateAuditLogEntry(AuditServiceImpl.java:78)
    ...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer (Write failed)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:3206)
	at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:2080)
Caused by: java.net.SocketException: Connection reset by peer (Write failed)
	at java.base/java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.base/java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:110)
	at java.base/java.net.SocketOutputStream.write(SocketOutputStream.java:150)
	at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyOutputStream.writeInternal(IOBuffer.java:1115)
	at com.microsoft.sqlserver.jdbc.TDSChannel$ProxyOutputStream.write(IOBuffer.java:1108)
	at java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:1304)
	at com.microsoft.sqlserver.jdbc.TDSChannel.write(IOBuffer.java:2075)
	... 103 more

Verify the stability and connectivity of the database server. Reboots or network failures can cause the errors seen in the logs. Ensure the database server operates smoothly without interruptions.
Once the database issues are resolved, please initiate the deployment.