Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mqtt-dup property handling #113

Open
Draczech opened this issue Jan 7, 2018 · 1 comment
Open

mqtt-dup property handling #113

Draczech opened this issue Jan 7, 2018 · 1 comment

Comments

@Draczech
Copy link

Draczech commented Jan 7, 2018

Setup Description

In my company's setup we use set of services (written in Java + Spring) running as Docker swarm containers. One of these services takes care of processing messages from IoT Hub, augmenting them and dispatching them to their respective destinations (mostly Service Bus queues).

When an event is read from IoT Hub, it is read by Event Processor Host and all of its application properties are copied while system properties are ignored apart from sender device ID.

When a message is sent to the receiver's queue, the Spring's JmsTemplate is used and BytesMessage is created with the payload and properties read from the initial event's application properties as well as properties collected during message augmentation are assigned to it as String properties.

Problem Description

Sometimes when trying to send the message via JMS tools to the Service Bus queue we get following JMSException:

Identifier contains invalid JMS identifier character '-': 'mqtt-dup'

I haven't found the specific messages causing this problem, but I presume that the mqtt-dup is used as value of the DupProperty and this property is assigned not as system property of an event, but as application property. Then this property slips through during reading the event from IoT Hub and causes incompatibility issues with JMS when trying to apply it to a JMS message.

I only found such property value used in iot protocol gateway code so that is why ask here if such problem is reald or if I should search for the root of the issue elsewhere. Thanks for any comment on this!

@Draczech
Copy link
Author

This issue was caused by the problem in azure-iot-sdk-csharp library and is now reported properly as issue 329 there. If you don't find any relevant connection to it in this project, feel free to close this issue.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant