Errors when accessing my app

Just had the following error when refreshing my app :

Backendless encountered an error while handling the request. An internal trouble ticket with ID EDA8A024-1E19-7C5F-FF45-E31802321800 has been created and we will be investigating the issue.
org.apache.http.conn.ConnectTimeoutException: Connect to bl-billing:8080 [bl-billing/10.43.34.66] failed: Connect timed out
java.lang.RuntimeException: org.apache.http.conn.ConnectTimeoutException: Connect to bl-billing:8080 [bl-billing/10.43.34.66] failed: Connect timed out
	at com.backendless.services.billing.BillingInteractor.getSubscriptionStatus(BillingInteractor.java:755)
	at com.backendless.monitoring.NamedPerformanceMonitoring.invoke(NamedPerformanceMonitoring.java:33)
	at com.backendless.services.billing.BillingInteractorCacheDecorator.getSubscriptionStatus(BillingInteractorCacheDecorator.java:244)
	at com.backendless.util.FileRequestHelper.getResponseForFileViewOrDownloadByClient(FileRequestHelper.java:96)
	at controllers.files.FilesApiController.lambda$downloadFile$12(FilesApiController.java:530)
	at com.backendless.util.FileRequestHelper.validateHostAndReturnResult(FileRequestHelper.java:179)
	at controllers.files.FilesApiController.lambda$downloadFile$13(FilesApiController.java:526)
	at com.backendless.services.ETagService.getCachedOrExecute(ETagService.java:36)
	at controllers.files.FilesApiController.downloadFile(FilesApiController.java:526)
	at controllers.files.FilesApiController.downloadFileOrExecuteScript(FilesApiController.java:521)
	at controllers.files.FilesApiController.lambda$action$11(FilesApiController.java:490)
	at com.backendless.async.BackendlessExecutorService.lambda$submit$0(BackendlessExecutorService.java:75)
	at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
	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:833)
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to bl-billing:8080 [bl-billing/10.43.34.66] failed: Connect timed out
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
	at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
	at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
	at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
	at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
	at com.backendless.services.billing.BillingInteractor.getSubscriptionStatus(BillingInteractor.java:750)
	... 15 more
Caused by: java.net.SocketTimeoutException: Connect timed out
	at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:546)
	at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597)
	at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
	at java.base/java.net.Socket.connect(Socket.java:633)
	at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
	at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
	... 27 more

Not sure what happened or what caused it.

Just refreshed again, and it works again.

Just encountered the error again.

Ji, @Nicolas_REMY

We are sorry for the inconvenience. Our team is working on it. This problem is of the highest priority for us.

Regards,
Marina

1 Like

Hello @Nicolas_REMY,

The issue has been fixed from our side.
Could you please check if it works fine now?

Regards,
Olha

Hi @olhadanylova ,

Yes, I haven’t encountered this issue since, thanks.

However, another one came up here : URGENT - UI app publication does not deploy to components/reusable!

Nicolas