Troubleshooting¶

Troubleshooting tips for AdapLink service and client¶

Start with looking at tomcat server log files at $AdapLink-Service\apache-tomcat\logs\.
Ensure firewall on client and server machines are not blocking port 8085.
Check if there are any significant change in hardware, like physical/virtual network adapters on the service machine. AdapLink uses this to perform license check.

At what stage is the client unable to connect?¶

Is it at the initial stage itself?

Ensure firewall on client and server machines are not blocking port 8085¶

Using Internet Explorer in the customer machine, try connect to URL similar to http://127.0.0.1:8085/alsc_service/xmlrpc but replaced with actual AdapLink Service machine IP and see the tomcat message.

If you get a web page message as shown below, it means Tomcat server is running and connecting from the client machine should be possible.

Check if there is enough hard disk space on the machine as log files are create on every run?¶

The same log files exist on both client and server machines. Currently they need to be cleaned manually.

Log file paths are:

On server: $AdapLink-Service\com.adaplink.service\WEB-INF\My_Logs\
On client: $AdapLink-Client\.AdapChainBase_cl\My_Logs\

How to view all AdapLink Service thread stack traces¶

There could be a case when we need to identify the live status of Java threads for AdapLink Service.

Download and copy the file view_thread_stacktrace.jsp to location $AdapLink-Service\download\.

With the help of your browser open URL http://adaplink-service-machine-ip:8055/download/view_thread_stacktrace.jsp.

Troubleshooting¶