| Field | Description |
|---|---|
| Ticket ID | AMM-1352 |
| Severity | Critical |
| Category | Bug |
| Affected Module / Feature | MMU |
Unable to do Data Sync. In the Production_APL offline MMU- while syncing the data, getting some error related to websphere application/Unexpected end of file from server
Use one or more of the following techniques for RCA:
5 Whys
Fishbone (Ishikawa) Diagram
Fault Tree Analysis
Log/Trace review
Primary Root Cause Identified: The data sync failed because large data batches exhausted server resources and the loop did not exit cleanly.
Why it happened: The sync logic didn’t handle big data and connection limits properly, causing the server to close the request unexpectedly.
Why wasn't it caught earlier? No large-volume load testing was done, and the error messages didn’t show the real issue.
| Action | Owner | Target Date | Status |
|---|---|---|---|
| Optimize batch size and implement proper exit conditions to handle large data safely | Vanitha | 2025-07-23 | Completed |
| Increase server connection timeout and tune DB pool settings | Vanitha | 2025-07-23 | Completed |
Immediate actions to resolve the issue and restore service.
| Action | Owner | Target Date | Status |
|---|---|---|---|
| Review and optimize sync logic in each release cycle | Vanitha | ||
| Schedule data sync to run frequently in smaller batches to prevent large payload failures. | Vanitha |
Systemic changes, monitoring, alerting, process updates, or automation.
Monitoring logs and metrics to confirm successful data syncs.
Checking for recurrence of I/O or timeout errors.
Confirming increased connection timeouts are sufficient during large syncs.
Implement batch processing for large data to avoid timeouts and failures.
Increase connection timeouts and server request handling capacity for heavy operations.
Schedule data syncs more frequently to reduce payload size and risk of failures.
| Reviewed By | Date | Remarks |
|---|---|---|