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
Hi,
operate as follow steps:
1.start a provider service and a consumer service
2.consumer service subscribe to provider's broadcast
3.restart consumer service
4.use provider service publish a broadcast information then consumer service will print the following log
2022-04-29 11:05:40,446 [DEBUG] HivemqMqttClient: (clientHash=5b69d40d, GBID=gwmsoagbid1, bidirectional): Received publication: topic: Hw7dWStkSjWXrc53EbAIRg/systemMessage, size: 528, qos: AT_LEAST_ONCE, retain: false, expiryInterval: 120. 2022-04-29 11:05:40,447 [DEBUG] MqttMessagingSkeleton: <<< INCOMING FROM gwmsoagbid1 <<< messageId: SUjiE8_-TZOMkwJiMBByZg, type: m, sender: Hw7dWStkSjWXrc53EbAIRg, recipient: Hw7dWStkSjWXrc53EbAIRg/systemMessage, expiryDate: 1651201660441, size: 528 2022-04-29 11:05:40,448 [ERROR] CcMessageRouter: ERROR SENDING: aborting send. Error: Failed to route multicast publication: No recipient found for given message: messageId: SUjiE8_-TZOMkwJiMBByZg, type: m, sender: Hw7dWStkSjWXrc53EbAIRg, recipient: Hw7dWStkSjWXrc53EbAIRg/systemMessage, expiryDate: 1651201660441, size: 528
the consumer's receiverid is not change,so I think it should receive the broadcast information rather than print error log
The text was updated successfully, but these errors were encountered:
The consumer service proxy must subscribe again after restart in order to be able to get and process publications from provider.
If the consumer services runtime is using same MQTT clientId as before after restart, it´s runtime might get publications sent by the provider which where queued at MQTT broker or sent later even if the consumer has not subscribed to broadcast after restart. This can be prevented by using cleanSession=true. In this case MQTT subscription which got established during first run of consumer service to implement the non-filtered joynr broadcast subscription as Multicast subscription via MQTT will get deleted. Of course using another not yet used clientId will also establish a fresh connection with no active subscriptions.
Hi,
operate as follow steps:
1.start a provider service and a consumer service
2.consumer service subscribe to provider's broadcast
3.restart consumer service
4.use provider service publish a broadcast information then consumer service will print the following log
2022-04-29 11:05:40,446 [DEBUG] HivemqMqttClient: (clientHash=5b69d40d, GBID=gwmsoagbid1, bidirectional): Received publication: topic: Hw7dWStkSjWXrc53EbAIRg/systemMessage, size: 528, qos: AT_LEAST_ONCE, retain: false, expiryInterval: 120. 2022-04-29 11:05:40,447 [DEBUG] MqttMessagingSkeleton: <<< INCOMING FROM gwmsoagbid1 <<< messageId: SUjiE8_-TZOMkwJiMBByZg, type: m, sender: Hw7dWStkSjWXrc53EbAIRg, recipient: Hw7dWStkSjWXrc53EbAIRg/systemMessage, expiryDate: 1651201660441, size: 528 2022-04-29 11:05:40,448 [ERROR] CcMessageRouter: ERROR SENDING: aborting send. Error: Failed to route multicast publication: No recipient found for given message: messageId: SUjiE8_-TZOMkwJiMBByZg, type: m, sender: Hw7dWStkSjWXrc53EbAIRg, recipient: Hw7dWStkSjWXrc53EbAIRg/systemMessage, expiryDate: 1651201660441, size: 528
the consumer's receiverid is not change,so I think it should receive the broadcast information rather than print error log
The text was updated successfully, but these errors were encountered: