-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Loopback 4 keep alive when datasource error #4358
Open
Labels
Description
Hello,
I use Loopback 4 framework in my app service. In my app service I have a principal datasource and 2 more external datasources(SQL server). Sometimes the external datasources are not available and the app service crash when called an endpoint that use there. I cannot control when datasource are available or not.
All datasources have the property "lazyConnect", but this property don't works to this situation.
Is there a way to prevent the appservice crashing when this happens?
Thanks
Metadata
Metadata
Assignees
Labels
Type
Fields
Give feedbackNo fields configured for issues without a type.