Troubleshooting the JSON Schema and Message Queue

If the JSON messages are not being generated by the relativeJsonSchema in a Tridium Jace, check whether the Service Maintenance Agreement has expired.

If data quality is poor and messages are not reaching DCH, it may be due to the message queue buffer size being exceeded and overflow messages being discarded. Check that the queue size is sufficient to handle at least 130% of the total number of expected messages per interval. In the Jace, this can be achieved by accessing the hidden size slot for the EngineCycleMessageQueue and increasing the size.

Data quality may can be impacted by insufficient time between messages arriving at the broker. It is recommended to leave a gap of 20-50ms between each message where possible. In the Jace, this can be achieved by accessing the rate slot of the EngineCycleMessageQueue and changing the rate. This rate is a pause in milliseconds between each engine cycle. This rate plus the engine cycle time is the average time between each message.

Data quality will be affected if there is insufficient time to publish all messages in the upload interval. This will lead to the message queue overflowing and messages being lost. Calculate the total time for all messages to be uploaded and check that this does not exceed the upload interval.