EDC 0.7.0+ → Azure Deployment → PolicyMonitor Default Services→ Cannot unwrap ThreadPoolExecutor

[jerzy-wachowiak]

EDC 0.7.0 Azure Deployment, Chart form HEAD edc070-tractusx-connector-azure-vault-controlplane

INFO 2024-05-01T13:12:09.160275028 Started Commons Connection Pool
INFO 2024-05-01T13:12:09.160328128 Started PolicyMonitor Default Services
🍄[2024-05-01 13:12:09] [INFO   ] Cannot unwrap ThreadPoolExecutor for monitoring from java.util.concurrent.Executors$DelegatedScheduledExecutorService due to java.lang.reflect.InaccessibleObjectException: Unable to make field private final java.util.concurrent.ScheduledExecutorService java.util.concurrent.Executors$DelegatedScheduledExecutorService.e accessible: module java.base does not "opens java.util.concurrent" to unnamed module @cb0ed20
INFO 2024-05-01T13:12:09.171962092 Started org.eclipse.edc.connector.policy.monitor.PolicyMonitorExtension
INFO 2024-05-01T13:12:09.172078491 Started API Core
INFO 2024-05-01T13:12:09.172142691 Started Jersey Micrometer Metrics
INFO 2024-05-01T13:12:09.172331491 Started Web DID
INFO 2024-05-01T13:12:09.17239629 Started org.eclipse.edc.iam.identitytrust.issuer.configuration.TrustedIssuerConfigurationExtension
INFO 2024-05-01T13:12:09.177329475 edc070-tractusx-connector-azure-vault-controlplane ready

Does 🍄 indicate some misconfiguration of the chart?

[suh-rao]

Any update on this? We also have same issue/exception comes up during start.

[suh-rao]

Issue got resolved by adding jvmargs. This was proposed solution from micrometer https://github.com/micrometer-metrics/micrometer/issues/2317 --add-opens=java.base/java.util.concurrent=ALL-UNNAMED Not sure will it cause any security issue as this module open for all now.

[github-actions[bot]]

This issue is stale because it has been open for 4 weeks with no activity.