Fail to start Dynamic-mapping-service

Forum
1

Product/components used and version/fix level:

Dynamic-mapping-service v4.1.4

Detailed explanation of the problem:

Error throws after dynamic-mapping-service start, that service is not available .
I have check the bootstrapUser for that micro-service application,
the name should be ‘servicebootstrap_dynamic-mapping-service’ , not ‘service_dynamic-mapping-service’ insteaded.

Error messages / full error message screenshot / log file:

2024-05-07 09:51:19.081 WARN 11 — [subscriptions-0] c.c.m.context.ContextServiceImpl : execution of task failed within tenant : t284731 - Http status code: 404
tenant: t284731 user: service_dynamic-mapping-service
2024-05-07 09:51:19.081 ERROR 11 — [subscriptions-0] c.m.s.s.MicroserviceSubscriptionsService : Http status code: 404
tenant: t284731 user: service_dynamic-mapping-service

com.cumulocity.sdk.client.SDKException: Http status code: 404
tenant: t284731 user: service_dynamic-mapping-service
at com.cumulocity.sdk.client.ResponseParser.checkStatus(ResponseParser.java:81)
at com.cumulocity.sdk.client.ResponseParser.parse(ResponseParser.java:63)
at com.cumulocity.sdk.client.RestConnector.get(RestConnector.java:118)
at com.cumulocity.sdk.client.PagedCollectionResourceImpl.get(PagedCollectionResourceImpl.java:130)
at com.cumulocity.sdk.client.PagedCollectionResourceImpl.get(PagedCollectionResourceImpl.java:125)
at com.cumulocity.sdk.client.PagedCollectionResourceImpl.get(PagedCollectionResourceImpl.java:116)
at dynamic.mapping.notification.C8YNotificationSubscriber.lambda$getNotificationSubscriptionForDevices$2(C8YNotificationSubscriber.java:398)
at com.cumulocity.microservice.subscription.service.impl.MicroserviceSubscriptionsServiceImpl.lambda$runForTenant$7(MicroserviceSubscriptionsServiceImpl.java:242)
at com.cumulocity.microservice.context.ContextServiceImpl.callWithinContext(ContextServiceImpl.java:78)
at com.cumulocity.microservice.subscription.service.impl.MicroserviceSubscriptionsServiceImpl.lambda$callForTenant$8(MicroserviceSubscriptionsServiceImpl.java:251)
at java.base/java.util.Optional.map(Optional.java:265)
at com.cumulocity.microservice.subscription.service.impl.MicroserviceSubscriptionsServiceImpl.callForTenant(MicroserviceSubscriptionsServiceImpl.java:251)
at com.cumulocity.microservice.subscription.service.impl.MicroserviceSubscriptionsServiceImpl.runForTenant(MicroserviceSubscriptionsServiceImpl.java:241)
at dynamic.mapping.notification.C8YNotificationSubscriber.getNotificationSubscriptionForDevices(C8YNotificationSubscriber.java:394)
at dynamic.mapping.notification.C8YNotificationSubscriber.initDeviceClient(C8YNotificationSubscriber.java:147)

Question related to a free trial, or to a production (customer) instance?

C8Y backend v1018.0.341

2

Hi @anon18601492

sorry for the late response. This error appears mainly on instances where the notification 2.0 API is not enabled e.g. Cumulocity Edge.
Normally you can ignore these messages, it should still work except the outbound mappings.

We have already improved that in the latest merge to development branch: Merge pull request #144 from SoftwareAG/feature/propertiesAsTenantOpt… · Cumulocity-IoT/cumulocity-dynamic-mapper@975651b · GitHub
Now it will check if the API is available and if not, deactivate the outbound mapping automatically. Also the outbound mapping can be disabled from the Mapper UI now so in all cases these errors should not appear anymore.

Release will follow soon but will be based on latest GA 1019 cumulocity Web SDK.

3

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.