Client-side UI issues
Client side UI issues means the issues which are coming in JavaScript, HTML and CSS. These issues come in client's browser.
On UI component, if you are performing any action and it is not working as expected e.g. you have clicked on a button and nothing is happened then may be a possiblity that JavaScript is giving an error. As we know our application is single page application so if any JavaScript error occurred then whole application will start giving error and you can get error on any other page as well.While working with application you may sometimes encounter issues such as misaligned elements, application not opening on a particular browser, abrupt dynamic behavior of the page, etc. These are client-side UI issues that you can try to troubleshoot by following the instruction given in this section.
| Expand |
|---|
| title | A component is not rendering properly on the browser. |
|---|
|
| Step | Possible reason(s) | Possible solution(s) | Remarks |
|---|
| 1 | Browser cache may not be working properly. | Clear the browser cache then retry again. | If not solved, follow the step 2. | | 2 | The browser or its version is not supported. | Try to open in a different version of the same browser, or in another browser altogether. | If it is working fine, get the browser name and version on which it not working so that developer can debug it. | | 3 | It may be a JavaScript issue. | A developer can debug such an error. | On the top-right corner, click the icon  Image Modified, and then More tools > Developer tools > Console,and download the console logs. This log would help Adeptia Connect debug the error. | Info |
|---|
| These are the steps to save the Chrome browser console logs. Refer to this page to know how to save other browsers' console logs. |
|
|
Server-side UI issues
To troubleshoot server Server-side issues you need to check the bowser's developer tool network tab. In some cases we are showing the alert message but in some cases it is not there. So if any HHTP request is failing then it is always recommended to check the network tab of developer tools of browser. Here you can get more information like URL, Request header Parameters , Response Header parameters and response.
In this network tab you need to see below things:
- Status code Request URL
- Request Header parameters
- Request PayLoad in case of PUT or POST method
- Response Header parameters
- Response
typically occur when the server either returns an erroneous response or doesn't respond at all to a request.
| Expand |
|---|
|
You can troubleshoot the server-side UI issues by investigating the HTTP status codes, Headers details, and the Response returned by the server. If server is not responding to your request, for example, you're unable to create a Template, you would need to go to the browser's More tools > Developer tools >Network. On this page, you'll find the URLs and their status codes under Status column, which would help you diagnose or fix the issue. HTTP Status Code | Possible reason(s) | Possible solution(s) | Remarks | 400 (Bad Request) | Your request path parameters or query parameters may not be valid. | Check the query and path parameters of your request. | For more details, you need to check your Webrunner logs. | 401 (Unauthorized) | - User session may have expired on the Connect Server either because you have been idle for a long time or the Webrunner has restarted.
- JWT token may have expired or you may have been idle for log time on the Connect Portal.
| Collect the Webrunner logs and provide it to Adeptia Connect for debugging the error. | For more details need to get the the Webrunner logs. | 403 (Forbidden) | You may not have the access to the resource or action in context. | Check if the role assigned to you has the required permissions. | For more details need to check the Webrunner logs. | 404 (Not Found) | The requested resource (image/CSS/JavaScript/HTML) may not be available or couldn't be found on the server. | Check if: - The Application(Portal /Server) is deployed properly or not.
- Patch has been applied properly on the Connect Server or not. Also check if you've performed the post deployment steps (if any) or not .
- Patch has been applied properly on the Connect Portal or not. Also check if every Connect Portal component have their own folder in "../ConnectPortal/webapps/wars” folder.
- If you are accessing the Connect portal then you need to check the Connect portal patch and root folder in the “../ConnectPortal/webapps/wars/root” folder similarly you can check for PD, Mapper, Schema Builder. Every component have their own folder in ../ConnectPortal/webapps/wars” folder.
|
| 500 (Internal Server Error) | An error may have occurred on the Connect Server. | - Collect the Webrunner logs and provide it to Adeptia Connect for debugging the error.
- Download the HAR file, and provide it to Adeptia Connect for debugging the error.
|
| 502 (Bad Gateway) | The Proxy/Load Balancer/Gateway may not be able to handle the response. | Check and correct the Load Balancer/Proxy/Gateway configuration. |
| 503 (Service Unavailable) | You may not have installed Adeptia Connect properly, and the Connect Server may not be ready to handle any request. | Check if: - The application(Portal /Server) is deployed properly or not.
- Patch has been applied properly on the Connect Server or not. Also check if you've performed the post deployment steps (if any) or not.
- If you are accessing the Connect portal then you need to check the Connect portal patch and root folder in the “../ConnectPortal/webapps/wars/root” folder similarly you can check for PD, Mapper, Schema Builder. Every component have their own folder in “.../ConnectPortal/webapps/wars” folder.
- The Webrunner and Portal logs have any relevant information.
|
| 504 (Gateway Timeout) | The Connect Server/Portal may not be able to respond within the stipulated time interval configured in the Proxy/Load Balancer/Gateway. | Increase the request time-out value in Load Balancer/Proxy/Gateway configuration. |
|
| Tip |
|---|
You can find the Webrunner logs at .../ConnectServer/AdeptiaServer/ServerKernel/logs/applicationlogs location of every node in a clustered environment. You can find the Portal logs (access_log, catalina.log, and application.log) in the Connect Portal at .../ConnectPortal/logs. |
- You can also get detailed information about the issue by clicking a URL – this takes you to Headers tab wherein you can find if there's a problem with any of the following headers.
- General
- Response Headers
- Request Headers
- Request Payload (if the used method is PUT or POST)
Expand each of the headers to see and verify the details. You can also export these details to an HAR file and send it to a developer to analyze and fix the issue. Refer to this page to know how to export or save the details to an HAR file. - To see if there's a problem with the response, go to the Response tab.
|
Common UI issues
This section discusses some common UI issues you may come across while working with the application.
| Expand |
|---|
| title | Connect Server and Portal are running, but the Portal UI is inaccessible. |
|---|
|
- Check if the URL (app.adeptia.host.url) of the Connect Server is mentioned correctly in the application.properties file located at the Connect Portal.
- In case you're using HTTPS scheme, you need to check if the certificates are configured properlyas per the deployment guidelines.
|
...
