No connection found to cluster Error

Bug
1

Hello,

We encountered an issue where all of our timers were stopped, and we couldn’t access the database.

Application ID: 4A47197B-AE30-FA84-FF56-0071F4010900
Error UID: BE55D90F-5485-4B35-A985-2A57682BFC09

Backendless encountered an error while handling the request. An internal trouble ticket with ID bl-server:BE55D90F-5485-4B35-A985-2A57682BFC09 has been created and we will be investigating the issue.
No connection found to cluster
com.hazelcast.client.HazelcastClientOfflineException: No connection found to cluster
	at com.hazelcast.client.impl.connection.tcp.TcpClientConnectionManager.checkInvocationAllowed(TcpClientConnectionManager.java:632)
	at com.hazelcast.client.impl.spi.impl.ClientInvocationServiceImpl.checkInvocationAllowed(ClientInvocationServiceImpl.java:294)
	at com.hazelcast.client.impl.spi.impl.ClientInvocation.invokeOnSelection(ClientInvocation.java:179)
	at com.hazelcast.client.impl.spi.impl.ClientInvocation.invoke(ClientInvocation.java:155)
	at com.hazelcast.client.cache.impl.ClientCacheProxySupport.getInternal(ClientCacheProxySupport.java:1069)
	at com.hazelcast.client.cache.impl.ClientCacheProxySupport.callGetSync(ClientCacheProxySupport.java:829)
	at com.hazelcast.client.cache.impl.nearcache.NearCachedClientCacheProxy.callGetSync(NearCachedClientCacheProxy.java:147)
	at com.hazelcast.client.cache.impl.ClientCacheProxy.get(ClientCacheProxy.java:503)
	at com.hazelcast.client.cache.impl.ClientCacheProxy.get(ClientCacheProxy.java:123)
	at com.backendless.cache.HazelcastCacheImpl.get(HazelcastCacheImpl.java:38)
	at com.backendless.data.validator.TableExistenceService.isTableExists(TableExistenceService.java:48)
	at com.backendless.data.validator.TableExistenceService.requireTableExists(TableExistenceService.java:71)
	at com.backendless.services.persistence.validator.TableExistenceDecorator.find(TableExistenceDecorator.java:202)
	at com.backendless.services.persistence.validator.TableExistenceDecorator.find(TableExistenceDecorator.java:36)
	at com.backendless.services.persistence.ContextServiceWrapper.find(ContextServiceWrapper.java:204)
	at com.backendless.rt.data.DataRTServiceDecorator$$EnhancerByGuice$$8bdc0f4.find(<generated>)
	at com.backendless.services.persistence.ContextServiceWrapper.find(ContextServiceWrapper.java:204)
	at com.backendless.services.persistence.common.DataAutomationEventsDecorator.find(DataAutomationEventsDecorator.java:365)
	at com.backendless.services.persistence.common.DataAutomationEventsDecorator.find(DataAutomationEventsDecorator.java:32)
	at com.backendless.services.persistence.common.PersistenceInterfaceAdapter.find(PersistenceInterfaceAdapter.java:209)
	at com.backendless.management.persistence.DirectManagemen

image
image827×179 20 KB

2

Closing this topic as resolved through Slack.

3

Hi @mark-piller ,

We encountered the same issue again, but this time we were still able to access the database.

image
image1316×612 40.3 KB

4

Hello @Francis_Bagas

We sincerely apologize for the inconvenience this issue has caused.

Please rest assured that our team is actively investigating the problem to identify the root cause and prevent it from happening again.

Thank you very much for your patience and understanding while we work on resolving this matter. We truly appreciate your cooperation.

Regards,
Volodymyr

5

Hi @Volodymy,

Thank you for checking on this and for the update. I appreciate the effort your team is putting into investigating the issue.

Additionally, we encountered another database issue where we were unable to access it. There are currently no errors showing in the logs, but access is not working on our end. Please let us know if you need any additional details from us to help with your investigation.

image
image932×346 34.3 KB

Thank you again for your continued support.

6

Thank you for your detailed update and for your cooperation.

Our DevOps team has addressed the issue, and I’ve verified from our side that both the application and database access are working correctly now.

Could you please check on your end and confirm that everything is functioning as expected?

We sincerely apologize for the inconvenience this situation caused and truly appreciate your patience while we investigated.

If you notice anything unusual or encounter the issue again, please don’t hesitate to reach out — we’ll be happy to assist right away.

Thank you again for your understanding.

Regards,
Volodymyr