如果在补偿服务的调用过程中发生失败，流程的补偿进程将被停止，并需要人工交互来重新启动。
If a failure occurs during invocation of a compensation service, compensation processing for this process is stopped and needs human interaction to be restarted.
例如，在Axis1中，用户必须手动调用管理客户机并更新服务器类路径，然后重新启动服务器以应用更改。
For example, in Axis1, users had to invoke the admin client manually and update the server class path, and then restart the server to apply the changes.
因此，在Axis 1. x中，用户必须手动调用管理客户机，并更新服务器类路径，然后重新启动服务器，以应用更改。
Therefore in Axis 1.x, the user has to invoke the admin client manually and update the server classpath, and then restart the server to apply the changes.
在早期测试中，我将服务器修改为在大约每三个系统调用中随机崩溃一次，用这种方法来测试重新启动功能。
During early testing, I ran pseudo with the server modified to randomly crash about one syscall in three, with the intent of carefully testing this functionality.
重新启动实例之后，这个外部存储过程库就会由DB 2在首次调用存储过程时被加载到内存中。
After restarting the instance, the external stored procedures library will be loaded in memory by DB2 on first invocation of the stored procedure.
同步——如果使用者在服务运行的过程中阻塞时崩溃了，当它重新启动时，将无法重新连接到正在进行的调用，所以响应丢失了。
Synchronous - If the consumer crashes while blocking as the service runs, when it restarts it has no way of reconnecting to the invocation in progress, so the response is lost.
如上所述，如果使用者在阻塞时崩溃，则即使它重新启动，响应也会丢失，因而必须重新进行调用。
And as explained earlier, if the consumer crashes while blocking, even if it restarts the response will be lost and the invocation must be repeated.
许多的新服务，如自动启动，热键调用，背光设置，时间同步，快捷按钮配置，手机重新启动，等等。
A plethora of new services, like autostart, hot-key invoke, backlight setting, time synchronization, shortcut button configuration, phone restart, and much more.
许多的新服务，如自动启动，热键调用，背光设置，时间同步，快捷按钮配置，手机重新启动，等等。
A plethora of new services, like autostart, hot-key invoke, backlight setting, time synchronization, shortcut button configuration, phone restart, and much more.
应用推荐