[INLONG-489] Add the maximum message length parameter setting

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Labels: pull-request-available
• Assignee: Guocheng Zhang
• Reporter: Guocheng Zhang
• Created: 03/Jan/21 12:31
• Updated: 25/Jul/22 08:35
• Resolved: 11/Jan/21 11:19

Description

At present, the maximum packet length of a message is set  through the TBaseConstants.META_MAX_MESSAGEG_DATA_SIZE and and the value can not be adjusted according to the needs during the running period. In an environment that exceeds the specified package length, we have to modify the value and recompile and publish the whole package, which brings trouble to the system operation and maintenance. If we can set the value according to the dynamically configurable topic, the operation and maintenance management of the system will become very simple

Issue Links

• links to: GitHub Pull Request #490
• links to: GitHub Pull Request #492
• links to: GitHub Pull Request #1078

Sub-Tasks

• Add configure store: Resolved
• Add setting operate API: Resolved
• Adjust max message size check logic: Resolved
• Add setting API interface document: Resolved
• Adjust the WebMethodMapper class interfaces: Resolved
• Adjust the packet length check when data is loaded: Resolved