Support #5238

Avatar?id=1733&size=50

[SCP ID :##2611##] : Request Order SD617764 & Change Order IM402992 : Toke Upload Error - Trade

Added by Ahmad Hazri over 9 years ago. Updated about 9 years ago.

Status:Closed - End of life cycleStart date:March 11, 2015
Priority:NormalDue date:
Assignee:Zahir Abd Latif% Done:

100%

Category:-Spent time:-
Target version:-

Description

Wei Quan

kindly assist below issue

User claim that they tried to upload dpx files 5 times but error shown asbelow. The dpx file contains 5k of token serial number. 
Last exercise, they hit the same errro but token is actually successfullyuploaded in RCAS system. 
1. Please check backend whether the token serial number have been loaded in thesystem or not. 
2. Please check with RCAS what caused the error.
logs in \\172.25.71.114\Deployment\AMSRCMS\SYSTEM\20150311

History

#1 Updated by Ong Wei Kuan over 9 years ago

  • Assignee changed from Ong Wei Kuan to Stephanie Sufrapto

Hi Stephanie,

Please assist on this issue. TQ.

#2 Avatar?id=1733&size=24 Updated by Ahmad Hazri over 9 years ago

  • Project changed from Maybank RCAS Support to Maybank BII RCAS Support
  • Description updated (diff)
  • Assignee changed from Stephanie Sufrapto to Ong Wei Kuan

#3 Avatar?id=1733&size=24 Updated by Ahmad Hazri over 9 years ago

  • Project changed from Maybank BII RCAS Support to Maybank RCAS Support
  • Assignee changed from Ong Wei Kuan to Stephanie Sufrapto

#4 Updated by Ong Wei Kuan over 9 years ago

  • Status changed from New - Begin Life Cycle to Development / Work In Progress
  • Assignee changed from Stephanie Sufrapto to Ong Wei Kuan

Issue Update :-

Root Cause:-
1. Token not uploaded into DB
- Pending approval from Checker.

2. Internal Server Error
- Token loading time from dpx file is 66 seconds, which exceed default server IO timeout 60 seconds.

Solution:-
1. After approved by checker, tokens were uploaded successfully into DB.
2. Had provided Bank with 2 solutions:
a. Break down the dpx file to 4K token per file, so that will not hit the server IO timeout with default value 60 seconds.
b. Disable the server IO timeout, just like current SIT and UAT.

Pending Customer Feedback and decision.

#5 Updated by Ong Wei Kuan over 9 years ago

  • Status changed from Development / Work In Progress to Pending Customer Feedback
  • Assignee changed from Ong Wei Kuan to Zahir Abd Latif

-Had proposed a new solution that will solve the current 4K file size limitation and also not dependent on the WebSphere IO timeout.

proposing to build standalone/batch token upload program that will be executed via scheduler (cron job). Below will be the process of the new solution:-
1) User upload the dpx file via RCAS Admin
2) The dpx file will be store to the local server designated folder
3) The transaction status will be "Pending Process"
4) After the scheduler kick off and processed the dpx file, the transaction status will change to "Processed" and will send email to inform to the requester on the status.
5) The dpx file will be deleted after processed.
6) Maker / Checker process will remain the same as current

Pros:
1) There is no limitation on the session timeout and IO timeout
2) Can schedule the best time to process the dpx file
3) To resolve the current file size limitation

Cons:
1) Only process based on the scheduled time (but can mitigate by schedule the job to run on every minute)
2) The is new scheduled process to run on the server
3) There is new maintenance on the new "cron job"

Pending customer feedback on this suggestion.

#6 Updated by Zahir Abd Latif about 9 years ago

  • Status changed from Pending Customer Feedback to Closed - End of life cycle
  • % Done changed from 0 to 100

Closed this issue at the moment while pending feedback from customer.

Also available in: Atom PDF