Debug and workaround for the ticket #8650142 & #8711487

Debug and workaround for the ticket #8650142 & #8711487

Issue:

      The mail fetching schedule thread might have went unresponsive. During mail fetching task checker, it identifies this and delete the existing schedule entries from DB and create a new one. However, the newly created one can't fetch mails as the entry in "runningSchedules" map haven't cleared. So, the newly created one is put in waiting state till the first one removes the entry from the map. Meanwhile, in another 30 mins, the checker thread identifies the delay and creates a new one again. This happens in a loop and no mails were fetched into the application.

Workaround:

     Sufficient logs weren't available to identify the root cause for this. So, we have come up with a temporary workaround. With this, mail fetching shouldn't stop as well we have added debug prints to identify the RCA for this.

1. Download the attached fjar file based on your build version.
2. Click here on steps to apply the fjar file.
3. Currently, the log files are overwritten in every 2 minutes. So, we have modified the logging.properties file to increase the number of serverout log files from 50 to 350. Go to application server "<server_home>/conf/" folder. Backup the logging.properties file already present. Download the attached logging.properties file (check the compatible file according to your build version) and place it in the "<server_home>/conf/" folder.
4. Once above steps were followed, restart the application service once.
5. If the checker schedule starts a new mail fetching schedule, a notification will be sent to the technicians configured under "Application error" notification rule. Find the image below for a sample notification.



So, configure yourselves and other required technicians in the above notification rule.

6. Once the configured technicians received this notification, kindly share such notification mail as ".eml" file and immediately zip the entire logs folder. Share us the logs zip file for analysis. If the size of the log file is huge, you can send it to us using our FTP link https://bonitas2.zohocorp.com/. Select the product as "ServiceDesk Plus" and ticket number as 8650142.

Note: This is a temporary workaround. Collecting the logs immediately and sharing it with us will help us to identify the RCA for this issue. Once the RCA is found, we can fix this issue and release it in a hot-fix.

Attached file and its build version compatibility

Build No
File Name
14006
14006_8711487.fjar

14006_logging.properties (Kindly rename to logging.properties once downloaded)
14103
14103_8650142.fjar

logging.properties

                    New to ADSelfService Plus?

                      • Related Articles

                      • Logout Debug

                        Fjars for Logout Debug
                      • Debug/Workaround for 8894713: Refreshing access token call gets stuck causing delay in Mail Fetching Schedule

                        Issue: Mail fetching schedule doesn't fetch new mails intermittently. On analysing logs, we could infer a http call to Token url to refresh the access token doesn't respond and the schedule thread is made to wait indefinitely for the response. This ...
                      • Debug fjar for the ticket 8451935

                        Issue: Empty mail is triggered from the SDP in a particular scenario Debug: Debug prints have been enabled in the attached fjar file. With this debug prints, we can identify the scenario from which such mails are getting triggered. Kindly follow the ...
                      • Debug: Fjar for debugging purpose related to 8544269 ticket

                        The reason for this issue is to be identified using more debug prints in the logs. Please follow the below steps to collect debug logs. 1. Login to Application and Navigate to Mail server settings (Incoming tab). Follow steps 2&3 if not done already. ...
                      • Debug for #7963428

                        Issue: Emails from particular mail address is getting appended to an already existing ticket. Since, logs weren't available during that time of issue, follow the steps in this article to isolate the logs Steps to apply this debug: 1. Download the ...