Support #7568

[SCP ID :##3952##] : KFH Malaysia IB System Availability

Added by Zahir Abd Latif about 7 years ago. Updated about 7 years ago.

Status:Closed - End of life cycleStart date:July 13, 2017
Priority:HighDue date:
Assignee:Zahir Abd Latif% Done:

100%

Category:MY RIBSpent time:-
Target version:-

Description

Hi,
Kindly attend below request.

We received concern from server admin team regarding the IB instance stability since there are reported transaction error and server admin need to restart the instance.

There were incident on 11/07/2017 whereby server admin have to restart (7310) at 3pm and another issue reported at 11++ pm. Server admin restart the instance (7510) on 12/07/2017 @12 midnight.

Kindly investigate and the logs are available at below path ( for 11/07/2017 ):
\\10.20.8.35\Internet Banking\IB_Issues_and_Logs\11072017_ib_issue

History

#1 Updated by Zahir Abd Latif about 7 years ago

  • Priority changed from Normal to High

#2 Updated by Zahir Abd Latif about 7 years ago

  • Status changed from New - Begin Life Cycle to Pending Customer Feedback
  • Assignee changed from Tan Jeng Wei to Zahir Abd Latif
  • % Done changed from 0 to 100

Norashikin, Jul 18, 2017 09:22 AM:-

Thank you for your feedback. We have forwarded to FPX vendor for their next action. 
Meantime, could you check on the logs ( requested by Hazri on 13/07/2017)  to see if other factors contribute to this issue. 

The logs are available at below path: 
\\10.20.8.35\Internet Banking\IB_Issues_and_Logs\13072017_https_kfhib01&2_logs

Jul 18, 2017 09:48 AM:-


Dear Shikin,
The reason we look into this direction is because seeing the "Out of memory" occurrences and there is no other suspicious error except the JMX connection error which had been raised 
to BV before and confirmed that it is for internal use and has no impact.

When JVM is out of memory, it will become unstable and require to restart. I would suggest for temporary, either you deploy the FPX to other servers or at at least only run on CONSUMER_FPX Instance 0 
and Instance 2, and BIB_FPX  on Instance 1 and Instance 3 to reduce the memory usage. 

Instance 0 = 30 out of memory occurrences
Instance 1 = 8 out of memory occurrences
Instance 2 = 12 out of memory occurrences
Instance 3 = 50 out of memory occurrences

#3 Updated by Zahir Abd Latif about 7 years ago

  • Status changed from Pending Customer Feedback to Closed - End of life cycle

Issue closed in SCP.

Also available in: Atom PDF