Support Article
Message blocked error occurs after migrating to AMP 5.7.21
SA-42025
Summary
Message blocked error occurs after migrating to AMP 5.7.21 Server (Business Gateway). This behavior is observed only in the AMP 5 Server compatibility mode with AMP 4 client.
Error Messages
com.vaultus.basiccommon.foundation.sync.SyncException: (ERR=0x0002000c=0:512:12) General error: (ERR=0x000100cd=0:256:205) Message blocked at com.vaultus.basiccommon.foundation.sync.SyncException.convertToSyncException(SyncException.java:103) . . . com.vaultus.vmsserver.core.sync.ServerPeerConnection.sendMessage(ServerPeerConnection.java:75) ... 17 moreSteps to Reproduce
- Upgrade from AMP 4.3.x Server (Business Gateway) to AMP 5.7.21 Server (Business Gateway)
- Log in to the AMP 5 server with AMP 4 client.
- Start a sync with amount of messages that exceed the configured or the default window size.
- Turn the device network connection off.
Root Cause
The Message Blocked error was a result of exceeding the window size (the number of Sent and Not Acknowledged messages) while sending messages to an AMP 4.3 client.
Resolution
Configuring the Message Send and Receive window size in the compatibility mode was added in the AMP 5.7.22. In the compatibility mode, the number of messages that AMP Business Gateway retains in the queue to be sent to the device without receiving ACKs, can be controlled. Configuring these parameters prevents messages from being blocked due to temporary network issues.Both the Message Send and Receive window size can be configured in the COMM section within the cluster.config configuration file:
[COMM]
TCP_SEND_WINDOW_SIZE = 50
TCP_RECEIVE_WINDOW_SIZE = 120
Tags:
Published November 8, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.