Error while deleting backendless app

Bug
1

Application ID: 0D36427B-54B9-D106-FF8E-C8329888D300
Error UID: 7D5ED491-6B07-1588-FFB4-B67146027E00

Backendless encountered an error while handling the request. An internal trouble ticket with ID 7D5ED491-6B07-1588-FFB4-B67146027E00 has been created and we will be investigating the issue.
org.hibernate.exception.SQLGrammarException: could not extract ResultSet
javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet
	at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:154)
	at org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1626)
	at org.hibernate.query.Query.getResultList(Query.java:165)
	at com.backendless.datamodel.dao.AbstractEntityDAO.lambda$findAll$8(AbstractEntityDAO.java:128)
	at com.backendless.datamodel.application.dao.AppJpaTransaction.executeSync(AppJpaTransaction.java:138)
	at com.backendless.datamodel.application.dao.AppJpaTransaction.executeSync(AppJpaTransaction.java:207)
	at com.backendless.datamodel.application.dao.AppJpaTransaction.lambda$execute$0(AppJpaTransaction.java:51)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
	Suppressed: java.util.concurrent.ExecutionException: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet
		at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
		at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999)
		at com.backendless.async.UncheckedCompletableFuture.getUnchecked(UncheckedCompletableFuture.java:25)
		at com.backendless.async.UncheckedCompletableFutureImpl.getUnchecked(UncheckedCompletableFutureImpl.java:29)
		at com.backendless.management.users.OAuth2ProviderService.getAll(OAuth2ProviderService.java:85)
		at com.backendless.management.appsettings.ManageAppSettingsService.getAppSettings(ManageAppSettingsService.java:176)
		at controllers.console.appsettings.ManageAppSettings.lambda$getAppSettings$0(ManageAppSettings.java:127)
		at com.backendless.async.BackendlessExecutorService.lambda$submit$0(BackendlessExecutorService.java:106)
		... 4 more
Caused by: org.hibernate.exception.SQLGrammarException: could not extract ResultSet
	at org.hibernate.exception.internal.SQLE

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.
(Note: Other newly created app’s are getting deleted but default app has an issue)

1.Create a default app using template
2.delete app
3.Throws error

2

Hello @Swapnil_Ghorpade

Could you specify which template you created?

3

I don’t remember exactly for which blueprint it’s not able to delete app.
I have created 2 app’s, on 2nd app expiry deleted that succesfully but forgot to delete first time created app which is expired now. so not even able to view/delete that app or create new one.
can’t see settings or anything related to that app.
Could you please help me to delete that app ?

4

Hello @Swapnil_Ghorpade!

Sorry for inconvenience.
I want to make sure I understand you correctly, you want to delete the application with the id 0D36427B-54B9-D106-FF8E-C8329888D300 (StackholderAnalytics)?

Regards,
Alexander

5

yes correct, Have to delete this (0D36427B-54B9-D106-FF8E-C8329888D300)

6

Yes, you please delete the same (StackholderAnalytics)

7

Thank you. I will write to you as soon as the app is removed.

Regards,
Alexander

8

@Swapnil_Ghorpade, your application has been deleted, once again we apologize for the inconvenience.

Regards,
Alexander

9

Thank @Alexander Pavelko for responding quickly.
Yes, it’s deleted and now I can create a new app without any problem.

1 Like