Why is my HRMS web app blocked when uploading files in TravelDesk?

HRMS Web App Blocked During TravelDesk File Uploads: A Shared Session Issue

This problem arises from the use of a single ASPState session database for both the /HRMS and /TravelDesk web applications. Large file uploads in /TravelDesk can take considerable time, resulting in a session lock within the SQL Server database. This lock prevents access to the /HRMS application until the upload is finished.

Understanding Session Locking

SQL Server's session management employs locking to maintain data integrity. When a user session is created, a lock is applied to prevent simultaneous modifications from multiple requests.

Root Cause Analysis

The file upload in /TravelDesk locks the user's session. Because both applications share the same session database, any subsequent /HRMS requests from that user are blocked while waiting for the /TravelDesk session lock to be released.

Solution: Disabling Session State

The most effective solution involves disabling session state for the specific /TravelDesk page or handler responsible for the lengthy file upload process. This prevents session locking during the upload, enabling concurrent access to /HRMS. The implementation would look like this (though the exact method may vary slightly depending on the framework):

<code>//Code to disable session state would go here (implementation depends on framework)</code>

The above is the detailed content of Why is my HRMS web app blocked when uploading files in TravelDesk?. For more information, please follow other related articles on the PHP Chinese website!