Use these tips to resolve errors caused by MicroBroker.
If you suspect that MicroBroker is the source of a problem, you can modify the MicroBroker trace level to receive more information.
To do this, set the trace.level property in the MicroBroker agent. Possible values for the trace.level property are min, 1, 2, 3, 4, 5, or max.
Increase the MicroBroker queue size if you are receiving MicroBroker warnings, such as the following:
[WARNING] FMBM1009 MicroBroker Client 'BridgeMicro' - queue 'bridge:E1-prem' is full. Depth: 1000
You can increase the MicroBroker queue size by editing the queueSize parameter in the MicroBroker agent.
Increase the MicroBroker queue size if you are receiving MicroBroker errors similar to the following examples.
XML with additional EPC URI data
[ERROR] FMBT1761 MicroBroker Client 'BridgeMicro' - PUBLISH MQTT protocol flow exceeds the maximum message size. Max size:51200 bytes, Message size:241047
XML without additional EPC URI data
[ERROR] FMBT1761 MicroBroker Client 'BridgeMicro' - PUBLISH MQTT protocol flow exceeds the maximum message size. Max size:51200 bytes, Message size:136139
Serialized object with additional EPC URI data
[ERROR] FMBT1761 MicroBroker Client 'BridgeMicro' - PUBLISH MQTT protocol flow exceeds the maximum message size. Max size:51200 bytes, Message size:154454
Serialized object without additional EPC URI data
[ERROR] FMBT1761 MicroBroker Client 'BridgeMicro' - PUBLISH MQTT protocol flow exceeds the maximum message size. Max size:51200 bytes, Message size:94374
You can increase the MicroBroker maximum message size by editing the maxMessageSize parameter in the MicroBroker agent.