Troubleshooting
You can check logs provided by the Alipay+ server SDK to obtain helpful information for troubleshooting. The log format depends on your logging framework configuration. Below is a sample log snippet:
2019-11-20:2019-11-20 23:58:05,635 INFO repository.impl.RouteConfigRepositoryImpl mobile-mock-wallet-saas-plugin_1.0.0.20191019 - [AC_SDK][STORAGE_CONFIG_SAVE_FAILED]
The following table lists the log keywords that are recommended to be monitored and suggested troubleshooting solutions:
Log keyword | Condition | Solution |
[AC_SDK][STORAGE_CONFIG_SAVE_FAILED] | Some error occurs when saving route configuration data to storage. | Check the log, which usually contains exception stack or error messages. |
[AC_SDK][STORAGE_CONFIG_READ_FAILED] | Some error occurs when reading route configuration data from storage. | Check the log, which usually contains exception stack or error messages. |
[AC_SDK][REMOTE_CONFIG_DOWNLOAD_FAILED] | Fail to pull route configurations. |
|
[AC_SDK][INVALID_REMOTE_IDENTIFICATION_RESULT] | Some error occurs when identifying the Alipay+ code. |
|
[AC_SDK][ROUTE_CONFIG_IS_INVALID] | The loaded route configuration is invalid or blank. |
|
[AC_SDK][SCHEDULER_THREAD_INTERRUPTED] | The thread which schedules updates is interrupted. | Check whether the thread scheduler can be interrupted in your integration code and you might restart your server to initialize the Alipay+ server SDK again. |
[AC_SDK][UNKNOWN_CODE] | Some error occurs when recognizing the Alipay+ code. |
|
Besides, the Alipay+ server SDK also logs unsuccessful API calls:
[AC_SDK][INVOKE_PROCESS_ERROR][resultCode: %s, message: %s]