Error while creating linked records

[Richard_Munger]

Application ID: DEC6B808-645B-7B62-FF97-8D7C3B617700
Error UID: 311A3662-E630-40DC-92DA-C3BACC4981B3

Backendless encountered an error while handling the request. An internal trouble ticket with ID bl-server:311A3662-E630-40DC-92DA-C3BACC4981B3 has been created and we will be investigating the issue.
com.mysql.cj.jdbc.exceptions.MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction
java.lang.RuntimeException: com.mysql.cj.jdbc.exceptions.MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction
	at com.backendless.persistence.RelationsService.deleteAllRelations(RelationsService.java:191)
	at com.backendless.persistence.RelationsService.lambda$setRelation$0(RelationsService.java:160)
	at com.backendless.datamodel.application.dao.AppJpaTransaction.executeSync(AppJpaTransaction.java:135)
	at com.backendless.datamodel.application.dao.AppJpaTransaction.executeSync(AppJpaTransaction.java:217)
	at com.backendless.datamodel.application.dao.AppJpaTransaction.execute(AppJpaTransaction.java:56)
	at com.backendless.datamodel.dao.JpaTransactionService.executeApp(JpaTransactionService.java:47)
	at com.backendless.persistence.RelationsService.setRelation(RelationsService.java:159)
	at com.backendless.monitoring.PerformanceMonitoring.invoke(PerformanceMonitoring.java:32)
	at com.backendless.services.persistence.internal.PersistenceService.lambda$setRelation$9(PersistenceService.java:620)
	at com.backendless.datamodel.application.dao.AppJpaContext.executeSync(AppJpaContext.java:228)
	at com.backendless.datamodel.application.dao.AppJpaContext.lambda$execute$0(AppJpaContext.java:54)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
	at com.backendless.async.BackendlessExecutorService.lambda$execute$1(BackendlessExecutorService.java:153)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)
	Suppressed: java.util.concurrent.ExecutionException: java.lang.RuntimeException: com.mysql.cj.jdbc.exceptions.MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction
		at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396)
		at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073)
		at com.backendless.async.AsyncUtils.safeGet(AsyncUtils.java:69)
		at com.backendless.services.persistence.internal.P

Problem description

Describe what you did in console that led to the error. Please provide a description of what actually happens. Be descriptive: “it doesn’t work” does not describe what the behavior actually is. This will help us with reproducing the problem.

Steps to reproduce

Please describe steps to reproduce starting from the first action.

[mark-piller]

This would help us help you:

[Richard_Munger]

App ID: DEC6B808-645B-7B62-FF97-8D7C3B617700

DB Table: Agents

Record object: 72758DC9-081A-45BD-9686-37C81AF482AA

Record Agent ID: 64

Description:

I had successfully created the DB record. I was then attempting to edit the record to add the data for linked fields (state, agenttype, paymententity, etc). Whenever the system displayed the popup screen to allow selection of the related values for the chosen field, the popup screen would lock and the DB errors messages would be displayed.

I then figured that the DB server was under maintenance or backup or some other internal process. I then logged out of BE and logged in again (to start a new process) to see if that would address the issue. It did not help.

[mark-piller]

I checked the record in your database and I see you were able to create links to other entities for that record:

[Richard_Munger]

Yes, the background DB issue seems to have subsided. The issue occurred multiple times and seems to be gone now…however system response time seems to be lagging today.

Thanks for looking into the issue.