Support #5380

Avatar?id=1733&size=50

[SCP ID :##2722##] : Unsuccessful eIBFT transaction after migration date 27/06/2015

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

Status:Closed - End of life cycleStart date:June 29, 2015
Priority:UrgentDue date:
Assignee:Zahir Abd Latif% Done:

100%

Category:-Spent time:-
Target version:-

Description

Kartono

Kindly attend this issue

Most eIBFT transaction was unsuccessful after migration on 27/06/2015.

Trnx details as below:

RIB Transaction Enquiry -Details
Transaction ID
20150629000003097370
Transaction Description
Favourite Instant Interbank Fund Transfer
Transaction Types
Favourite eIBFT Transfer
Customer Name
NADIRAH BINTI HASAN
Transaction From Account No
1006411000109690
Transaction To Account No
163019615601
Amount
2,500.00
Effective Date
29/06/2015
Transaction Date
29/06/2015 08:55:06 AM
Transaction Status:
Unsuccessful
Host Error Reason:
-
RRN2:
-
[6/29/158:55:06:064 SGT] 00000082 SystemOut     O Socket input data(in Hex): [29/06/2015] [08:55:06:111] [ERROR][IBInterbankFundTransferResultsServices]:527 - Error code : 9999
[6/29/158:55:06:111 SGT] 00000035 SystemOut     O [29/06/2015][08:55:06:111] [ERROR] [IBInterbankFundTransferResultsServices]:527 - Errordetails : java.lang.NullPointerException
      at com.ib.enterprise.services.ib104_fundtransfer.others.IBTransferLimitConstant$ServiceCode$3.getTrasferLimit(IBTransferLimitConstant.java:131)
      atcom.ib.enterprise.services.ib104_fundtransfer.IBFundTransferSevices.getUserTransferLimit(IBFundTransferSevices.java:678)
      at com.ib.enterprise.services.ib104_fundtransfer.IBFundTransferSevices.checkTransferDailyLimitByServiceCode(IBFundTransferSevices.java:568)
      atcom.ib.enterprise.services.ib104_fundtransfer.interbank.transfer.IBInterbankFundTransferResultsServices.execute(IBInterbankFundTransferResultsServices.java:221)
      atcom.ib.rib.controller.actions.ib104_fundtransfer.interbank.transfer.IBInterbankTransferResultsAction.execute(IBInterbankTransferResultsAction.java:103)
      at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
      at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
      at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
      at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
      at com.ib.common.utils.IBActionServlet.doPost(IBActionServlet.java:82)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
      at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1661)
      atcom.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1602)
      atcom.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:149)
      atcom.ib.common.utils.SessionTimeoutFilter.doFilter(SessionTimeoutFilter.java:85)
      atcom.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
      at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125)
      atcom.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:80)
      atcom.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
      atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
      atcom.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:507)
      at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
      atcom.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
      at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:878)
      at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
      at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:191)
      atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
      atcom.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
      at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
      atcom.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:84)
      atcom.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
      atcom.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
      atcom.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
      at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
      at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
      atcom.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
      at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1656)

A - SystemOut_15.06.29_09.06.42.log (94.8 KB) Zahir Abd Latif, June 30, 2015 09:00

SIT Testcase to Penril.docx (1.11 MB) Zahir Abd Latif, August 07, 2015 11:09

RIB_SIT.LOG (187 KB) Zahir Abd Latif, August 07, 2015 11:09

History

#2 Updated by Zahir Abd Latif about 9 years ago

  • Status changed from New - Begin Life Cycle to Development / Work In Progress

#3 Updated by Zahir Abd Latif about 9 years ago

Update from Ruzaimah, Jul 2, 2015 03:10 PM:-

Temporary solution - update db and user has confirm issue resolved.

update IB_TRANSFER_LIMIT
set IBFT_OPEN_LIMIT=0
where IBFT_OPEN_LIMIT IS NULL

Kindly check for permanent solution.
From where and when system add/update IBFT_OPEN_LIMIT for IBFT_OPEN_LIMIT ? System should default to 0 for this field.

#4 Updated by Ngoh Chee Ping about 9 years ago

Permanent solution: Default the limit field to 0 in hibernate mapping file. Kartono will test it out in development first.

TQ

#5 Updated by Zahir Abd Latif about 9 years ago

Updated from Kartono, Jul 16, 2015 07:07 PM:-

Hi Ruzaimah,

The solution has already been deployed in SIT and UAT environment.
http://10.6.6.20/rib.sit/common/Login.do
http://10.6.6.20/rib.uat/common/Login.do

#6 Updated by Zahir Abd Latif about 9 years ago

Updated from Ruzaimah, Aug 6, 2015 05:23 PM:-

We have successfully registered new customer but when click Fund Transfer Limit - *still got Session Expired.*
Attached the result.

Dear Kartono,

Kindly assist on this issue.

Thanks.

#7 Updated by Zahir Abd Latif about 9 years ago

  • Status changed from Development / Work In Progress to Pending Customer Feedback

Update from Ruzaimah, Aug 11, 2015 10:49 AM:-

SIT successfully tested. Will send for UAT.

#8 Updated by Wijaya Kartono about 9 years ago

  • Status changed from Pending Customer Feedback to Pending Prod Deployment

Update from Ruzaimah, Aug 13, 2015 05:27 PM:-

"UAT Succeeded. Plan to migrate tomorrow 12.00 am as usual due to production issue and has been raised up to higher management.

Kindly send us the deployment doc asap."

#9 Updated by Zahir Abd Latif about 9 years ago

  • Status changed from Pending Prod Deployment to Closed - End of life cycle
  • Assignee changed from Wijaya Kartono to Zahir Abd Latif
  • % Done changed from 0 to 100

Deployment successful.
Issue closed in SCP.

Also available in: Atom PDF