Support #10549
[SCP ID :##5214##] : BIB - transaction history loading & hit internal server error
| Status: | Work Completed-End life cycle | Start date: | December 24, 2019 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Stephanie Sufrapto | % Done: | 100% | |
| Category: | BIB | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
Please look into this issue urgently, we have face this issue twice on 19/12/2019 and today 24/12/2019. Based on checking BIB1 server cause high CPU usage.
System back to normal after restart.
History
#1
Updated by Stephanie Sufrapto over 4 years ago
- Assignee changed from Stephanie Sufrapto to Chun Feng Lim
Hi CF.
Please help to look into this. it should go to another server if one server it's too heavy.
#2
Updated by Stephanie Sufrapto over 4 years ago
- Status changed from New - Begin Life Cycle to Work Completed-End life cycle
- Assignee changed from Chun Feng Lim to Stephanie Sufrapto
- % Done changed from 0 to 100
1) Out of memory
Root Cause: Our finding is one of the users did many request for the download SAGA statement in just 1 second which contributed the server to generate the many 3 months statement at the same time which cause out of heap memory.
Solution: Apply overlay to prevent user to make multiple click.
2) Internal Server Error
Root Cause: Due to network time out set at the Web/App server (60) and other server network timeout (120) are not tally.
Solution:
1) Update the Web server time out from client to 300 seconds.
2) Update the Web Server to App Server timeout to 120 seconds.
3) Setup datasource SQL Query timeout to 120 second (as recommended by IBM to set to similar to Database timeout value)
4) Migrate the STATIC error page to handle 404 and 500 error