This topic describes how to resolve the issue where Enterprise Distributed Application Service (EDAS) application pages are unavailable and Remote Procedure Call (RPC) calls fail.
EDAS application pages cannot be visited by using HTTP, and RPC calls fail.
- An error occurred in the network or the application or the application configuration path was invalid.
- The network between the instance and the registration center was unreachable, you did not have the permissions for the service, or the RPC call timed out.
- If EDAS application pages cannot be visited by using HTTP, perform the following steps:
- Run the
curl or pingcommand to check whether the page URL is valid. If the URL is valid, check whether the network connection from the access host to the server host is normal. If the network connection is abnormal, resolve the network issue and try again.
- If the network connection is normal, check whether an error is contained in the Tomcat log file. Make sure that all log errors are resolved.
- Make that the HTTP path is valid, especially the settings of the context and port number.
- Run the following command to view the process ID of the Java program:
ps -ef |grep java
- Sequentially run the following commands on a JVM tool to check whether the Java program
runs as expected.
sudo jstack -F process ID sudo jstat -class [vmid] [interval] [count]; jmap -heap 2083
- [vmid]: the process ID of the Java program.
- [interval]: the interval, in seconds or milliseconds.
- [count]: the number of printing times. If the default value is used, printing is ceaseless.
- Run the
- If a RPC call fails, perform the following steps:
- Check whether the application that makes the RPC call and the application that is released belong to same account and the network is reachable. Check whether the service is unavailable because the server port is blocked.
- Check whether an error is contained in the Tomcat application logs of the service. Make sure that all log errors are resolved until you can find the service in the service list.
- View the /home/admin/logs/hsf/hsf.log file to identify the error code. For the specific error and solution, see Error code: HSF-0001.