Support #4074
SCP ID : 1914 - Different account data profile upon first time login
| Status: | Closed - End of life cycle | Start date: | January 13, 2014 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: |  Tan Lee Yong | % Done: | 100% | |
| Category: | - | Spent time: | 40.00 hours | |
| Target version: | - |
Description
Dear Penril Support,
MPI Currently having some production issue, the problem happened when 2 transaction occur on same time.
This is the scenario
Customer 1 :ANNA MAE ROMERO AVENIDO do the first time login on 2013/12/18 17:03:31:113
Customer 2 :CHARINA DUJALI WHITE do the first time login on 2013/12/18 17:03:31:110
However Anna get all Charina's data during the successful first time login.
History
#1
Updated by Tan Lee Yong over 10 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- Assignee changed from Nazri Imran to Mohd Hashim Mohd Hadzrul
There is no production source code. Any finding or proposed solution will only able to go in together with the MPI Revamp project
#2
Updated by Mohd Hashim Mohd Hadzrul over 10 years ago
- Status changed from Development / Work In Progress to Closed - End of life cycle
- Assignee changed from Mohd Hashim Mohd Hadzrul to Tan Lee Yong
- % Done changed from 0 to 100
Previously, the ID was produced by java Random API. With this implementation, the risk of having duplicate values are high. By having a duplicate values in JMS, the response might go to the wrong producer/sender. Therefore, we can relate this theory with this "wrong account info" issue. Because of the complication with the existing source code, it is enough to release this fix to the production environment.
Interim solution: Generate message ID with a combination of milisecond, nanosecond and Java GUID (converted to Base64 to make it shorter). This can guarantee the uniqueness of the JMS Message ID.
There are some areas that can be improved on the existing JMS implementation. This can be an ultimate solution to this issue. But this solution require some changes within multiple areas in MPI environment. Because of the complication with the existing source code, we can ONLY compile this changes in Batch 3 source code. As agreed, this solution will be delivered together with Batch 3 in the future.
Ultimate solution: Will no longer use the "manually generated" Message ID. System will take generated Message ID by JMS itself. The sender will expect an ID when sending the message (instead of providing a custom Message ID) and this ID will be used by the receiver to pick up the correct message. JMS will make sure the uniqueness of the ID.