Support #5092
[SCP ID :##2519##] : Prod Isuues - HD00015700 - IBG Failure to credit.
| Status: | Closed - End of life cycle | Start date: | December 29, 2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | MY IBG | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
We are unable to cancel IBG Transaction at CORUS where we get "failed" upon confirmation.
History
#1
Updated by Norhaidah Md Dasuki over 9 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
Unable to replicate this scenario in development / staging environment. According to user (Sara) this issue is happening for the first time. After NBPS migration, they had tried to Cancel IBG transactions and was Successful. User also confirm no implementations was done in Production.?
29/12 - We request the logs for both application and esb.(rec.IB Log on 29/12). Request the production properties files at path \kfh_corus\src\my\com\cst\resources\parameter\(rec.30/12)
30/12 - Request on the library files at path /JBoss/lib for all instance.
31/12 - Received the details transaction where IBG failed to canceled from User. Clarification on user perform the cancellation
Still pending on library files at path /JBoss/lib for all instance and esb log request for dated 29/12/14 from IT.
#2
Updated by Ngoh Chee Ping over 9 years ago
Already received the JBoss libraries, it same as development. Therefore i suggest to restart server and clear cache. Maybe something had been cached, make the class not able to load.
#3
Updated by Norhaidah Md Dasuki over 9 years ago
- Status changed from Development / Work In Progress to Pending Customer Feedback
14/1/15 - below are the findings from our investigation on the issue. Email IT on the direction for next action.
Not application logic issue:
1. Tested will production source code in development. Able to cancel IBG successfully.
2. Tested will production library in development. Able to cancel IBG successfully.
3. Tested will production source code and library in development. Able to cancel IBG successfully.
Not Integration lost between IB and Core Banking
1. Checked the error log, and found that the error is class loader problem. Mean not able to load a class. If integration lost between IB and Core Banking, it should have connection error like "connection refused", "timeout", or "Not able to connect".
2. Normally class loader problem because of some problem on that JBoss serveruntil it cannot load that class file. In order to prove this, we requested to test in different instance.
Error Log:
2014/12/29 11:12:29:479 ERROR cst.enterprise.services.GenericESBServicesImpl: Error details : null
Exception class : org.apache.catalina.loader.WebappClassLoader, class method : findResourceInternal, line number : 1963org.apache.catalina.loader.WebappClassLoader.findResourceInternal(WebappClassLoader.java:1963)
org.apache.catalina.loader.WebappClassLoader.findResource(WebappClassLoader.java:929)
#4
Updated by Tan Lee Yong over 9 years ago
Correction:
Not application logic issue:
1. Tested with production source code in development. Able to cancel IBG successfully.
2. Tested with production library in development. Able to cancel IBG successfully.
3. Tested with production source code and library in development. Able to cancel IBG successfully.
#5
Updated by Tan Lee Yong over 9 years ago
Suggestion action with suspect of CORUS build at KFHIB03 is corrupted:-
- From now on, KFH Admin can only login CORUS at BV_Framework03 or BV_Framework04, don't access CORUS at BV_Framework01 and BV_Framework02.
- If there is no issue on IBG transaction cancellation, this can prove that there is something wrong on the JBOSS at KFHIB03.
- If IBG cancellation works on KFHIB04, then we can suspect the CORUS build at KFHIB03 is corrupt. We need to copy the KFHIB04 build to KHFIB03
#6
Updated by Zahir Abd Latif over 9 years ago
Dear All,
Any update on this case?
Thanks.
#7
Updated by Norhaidah Md Dasuki over 9 years ago
- Assignee changed from Hafizudin MD to Zahir Abd Latif
- % Done changed from 0 to 90
Update by Lee Yong on IBG Issue to KFH on 6/2/2015
Root cause :
Corus cannot retrieve profile from esb/phoenix
Resolution:
Our suggestion esb need to restart.
Already send email to IT to closed the issue.
#8
Updated by Zahir Abd Latif over 9 years ago
- Status changed from Pending Customer Feedback to Closed - End of life cycle
- % Done changed from 90 to 100
Issue closed in SCP.