Support #8036
SCP ID :##4249##] : [RMBP] JVM high and Http error
| Status: | Closed - End of life cycle | Start date: | October 31, 2017 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
please investigate, we are facing production issue for RMBP:
1. JVM high utilisasi
2. http error
please refer attachment for those 2 issues,
notes:
this issue already escalated to Pak Tek Keng and Pak Iyus
History
#1
Updated by Zahir Abd Latif almost 7 years ago
Dear Gabby,
Any update on this issue?
Please do update whether I can close this case.
Thanks.
#2
Updated by Zahir Abd Latif over 6 years ago
- Status changed from New - Begin Life Cycle to Closed - End of life cycle
- Assignee changed from Rayvandy Gabbytian to Zahir Abd Latif
- % Done changed from 0 to 100
Gabby, On 2 Nov 2017, at 12.36:-
Dear Pak Paulus, Below is yesterday's minutes of meeting. Our response is highlighted in blue. Location: SS3 3rd Floor, Pak Novi’s room Time: ~10:00 - 11:30 Attendees: - Pak Ignatius - Pak Paulus - Pak Ghulam - Pak Rudhi - Gabby Minutes: - RMBP JVM high usage, need Penril to investigate and provides solution, [Penril]: - We have analyzed and also report to Pak Ignatius team on the high memory usage and memory growth on the Rhino engine that used by IBM Worklight. MBI need to seek IBM to look into this matter, - We also reported to Pak Ignatius team that the RMBP code that was written by previous IT solution vendor is poorly written and designed, especially too many global variables and also a lot information should be passed from the Mobile App rather than store on the server session on the global variables. This require CR to re-code the entire RMBP and also RMBP Adaptor (both were coded by I2S), - We will guide you to turn on the session monitoring feature in Websphere in the development server for us to monitor and further understanding. - Pak Ignatius requests to move to transaction limit checking from result to confirm page (all modules both M2U & RMBP). Purpose: better user experience. This will results in removal of the limit error record from DB, and move to log instead, - Bank requests to build new table for limit, instead of calculating from IB_USER_TRANSACTION_HISTORY, - Pak Ignatius requests to add M2U error code. Purpose is to ease IT team pull the unsuccessful record and categorise the error into excel file. IT team does not want to use MSS. [Penril]: All above items required MBI to submit BRD in order for us to provide the requested changes. Thank you.
Issue closed in SCP.