The reason for the crash is becauss the SQL database connectivity was lost.
It's looks like this while checking the log file :
[15:54:58:066]|[10-11-2018]|[SYSERR]|[INFO]|[72]: 101603933 [ServiceDeskCommon-2] WARN tm.TransactionImpl - XAException: tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=PIF-SDP-01//46129, BranchQual=] errorCode=XA_UNKNOWN(0)
org.jboss.resource.connectionmanager.JBossLocalXAException: Error trying to start local tx: ; - nested throwable: (org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLException: I/O Error: Connection reset by peer: socket write error))
at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.start(TxConnectionManager.java:654)
at org.jboss.tm.TransactionImpl.startResource(TransactionImpl.java:1196)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (java.sql.SQLException: I/O Error: Connection reset by peer: socket write error)
Solution: We can enable the Read committed Snapshot in the MSSQL environment to increase the performance of the application.
Please follow the instructions:
1. Stop the service desk service.
2- Now execute the below queries one by one to enable the snapshot on the SQL server.
ALTER DATABASE <db_name> SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE <db_name> SET READ_COMMITTED_SNAPSHOT ON
3. Start the service and observe the behaviour.