You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to set up a simple connector sample, the build was successful. However, upon attempting to run it, the connector started successfully but then instantly shut down.
Expected Behavior
The connector should start and remain active, ready to accept requests as described in the documentation.
Observed Behavior
WARNING 2024-08-14T21:44:42.30297 The runtime is configured as an anonymous participant. DO NOT DO THIS IN PRODUCTION.
WARNING 2024-08-14T21:44:42.314673 edc.runtime.id is not configured so a random UUID is used. It is recommended to provide a static one.
INFO 2024-08-14T21:44:42.358684 Initialized Boot Services
INFO 2024-08-14T21:44:42.371427 Initialized Core Default Services
INFO 2024-08-14T21:44:42.403198 HTTPS enforcement it not enabled, please enable it in a production environment
INFO 2024-08-14T21:44:42.486756 HTTPS enforcement it not enabled, please enable it in a production environment
INFO 2024-08-14T21:44:42.488135 Initialized Core Services
WARNING 2024-08-14T21:44:42.552145 Settings: No setting found for key 'edc.hostname'. Using default value 'localhost'
WARNING 2024-08-14T21:44:42.552372 Using the InMemoryVault is not suitable for production scenarios and should be replaced with an actual Vault!
INFO 2024-08-14T21:44:42.552514 Initialized org.eclipse.edc.connector.core.SecurityDefaultServicesExtension
WARNING 2024-08-14T21:44:42.556437 There were missing service registrations in extension class org.eclipse.edc.connector.core.LocalPublicKeyDefaultExtension: org.eclipse.edc.keys.spi.LocalPublicKeyService
INFO 2024-08-14T21:44:42.556523 Initialized org.eclipse.edc.connector.core.LocalPublicKeyDefaultExtension
INFO 2024-08-14T21:44:42.557115 Prepared Boot Services
INFO 2024-08-14T21:44:42.55718 Prepared Core Default Services
INFO 2024-08-14T21:44:42.558161 Prepared Core Services
INFO 2024-08-14T21:44:42.558229 Prepared org.eclipse.edc.connector.core.SecurityDefaultServicesExtension
INFO 2024-08-14T21:44:42.559463 Prepared org.eclipse.edc.connector.core.LocalPublicKeyDefaultExtension
INFO 2024-08-14T21:44:42.559639 Started Boot Services
INFO 2024-08-14T21:44:42.559695 Started Core Default Services
INFO 2024-08-14T21:44:42.559746 Started Core Services
INFO 2024-08-14T21:44:42.559788 Started org.eclipse.edc.connector.core.SecurityDefaultServicesExtension
INFO 2024-08-14T21:44:42.559832 Started org.eclipse.edc.connector.core.LocalPublicKeyDefaultExtension
INFO 2024-08-14T21:44:42.560465 Runtime 2dad895f-254d-49a4-8e5b-33d0b8b3d18f ready
INFO 2024-08-14T21:44:42.560933 Shutdown org.eclipse.edc.connector.core.LocalPublicKeyDefaultExtension
INFO 2024-08-14T21:44:42.560988 Shutdown org.eclipse.edc.connector.core.SecurityDefaultServicesExtension
INFO 2024-08-14T21:44:42.561035 Shutdown Core Services
INFO 2024-08-14T21:44:42.561076 Shutdown Core Default Services
INFO 2024-08-14T21:44:42.561119 Shutdown Boot Services
INFO 2024-08-14T21:44:42.561162 Shutdown complete
hey, thanks for reporting, apparently the reason is that no threads have been launched so the runtime have nothing that keeps it alive.
A short fix would be to add a dependency like implementation(libs.edc.http), that will make the runtime running.
It looks to be caused by the fact that the previous implementation of the HealthCheckService (one of the services provided by the boot module) was scheduling threads, but now it's not doing it anymore.
Bug Report
Describe the Bug
When trying to set up a simple connector sample, the build was successful. However, upon attempting to run it, the connector started successfully but then instantly shut down.
Expected Behavior
The connector should start and remain active, ready to accept requests as described in the documentation.
Observed Behavior
Steps to Reproduce
Steps to reproduce the behavior:
Note: No changes have been made to the source code.
Context Information
The text was updated successfully, but these errors were encountered: