Problem description
Prerequisites:
The client is connected to the Mobile Gateway Service (MGS) component.
The backend application API service is configured in the MGS console.
Symptoms:
The client makes an RPC call but does not receive the expected result.
Common error types:
MGS returns no response (client-side error).
MGS returns no response (timeout).
MGS returns a response, but the result code indicates an error.
MGS returns a response with no errors, but the return value is not as expected.
Troubleshooting steps
The basic troubleshooting steps for the four common error types are as follows:
MGS returns no response (client-side error):
Determine the source of the error from the client exception details.
Check for connection issues.
Check for type conversion issues.
Check for null value issues.
Check for network issues.
MGS returns no response (timeout):
Timeout scenarios can be complex. A timeout can be caused by client timeout settings, intermediate device timeout limits, MGS gateway API timeout settings, or backend application server timeout settings.
When a timeout occurs, first identify its source (client, network, or server-side). Then, reproduce and analyze the issue for that specific scenario.
MGS returns a response, but the result code indicates an error:
See Gateway result codes to determine the source of the problem.
Gateway-side error codes usually relate to MGS client or server-side configurations, such as permissions, encryption and decryption, signature verification, and API rate limiting. Based on the error, check the connection type, signature verification configuration, and encryption and decryption configuration.
Business-side error codes usually relate to the backend application service. Check the backend application service logs for errors or exceptions.
MGS returns a response with no errors, but the return value is not as expected:
This type of problem is often related to the application logic.
Check if the mapping between request values and return values is correct.
Check if the backend application service receives the correct request values.
Check if the backend application service processes the request values correctly.
Check if the backend application service returns the correct data format.
Tools and methods
When troubleshooting gateway call issues, you may need to capture HTTP data packets or network packets for analysis.
For methods and tools to capture HTTP data packets, see How to capture HTTP messages.
For methods and tools to capture network packets, see How to capture network packets.