Support #5747
[SCP ID :##2868##] : SI cancellation error.
| Status: | Closed - End of life cycle | Start date: | November 27, 2015 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: |  Hafizudin MD | % Done: | 100% | |
| Category: | MY RIB | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:
We received a complaint from a customer that cannot proceed to cancel her SI. The page displayed 'Error While Performing Your Request' when tried to cancel the SI.
Since the SI is scheduled today, we have manually updated the status to become inactive SI to prevent the SI from executing. This is one off (pay later) SI mode type.
FYI, this is a repetitive case for the same customer. Seek your help to investigate and advise accordingly.
Below is the details:
Acc No : 001103010689
Bene Acc No : 171405649700000
Beneficary Bank : OCBC
Amount : RM3648.00
History
#1
Updated by Zahir Abd Latif over 8 years ago
- Status changed from New - Begin Life Cycle to Pending Customer Feedback
Update by Hafiz, Dec 21, 2015 02:30 PM:-
Hi Tahir/Ashikin Base of our finding. We found error about job name for scheduler is null(see log). This job name is set by value Oid at ib_si table. Please execute be below sql and return the result. Schema BVUSRPRD select ^ from IB_SI where CURRENT_TRNX_ID='201511250002239562';
LOG
2015/11/25 10:57:56:222 ERROR enterprise.services.ib112_si.IBSISummaryServices: Error code : 0000
2015/11/25 10:57:56:240 ERROR enterprise.services.ib112_si.IBSISummaryServices: Error details : Job name cannot be null or empty.
Exception class : org.quartz.Trigger, class method : setJobName, line number : 424org.quartz.Trigger.setJobName(Trigger.java:424)
net.penril.scheduler.job.SIEngine.generateTriggerData(SIEngine.java:352)
net.penril.scheduler.job.SIEngine.getFireTimeAfter2(SIEngine.java:100)
net.penril.scheduler.job.SIEngine.getFireTimeAfter(SIEngine.java:71)
net.penril.scheduler.job.SIEngine.getNextPaymentDate(SIEngine.java:198)
my.com.kfh.enterprise.services.ib112_si.IBSISummaryServices.getSISummary(IBSISummaryServices.java:257)
my.com.kfh.controller.actions.ib112_si.IBSISummaryAction.execute(IBSISummaryAction.java:109)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
my.com.kfh.web.utils.IBActionServlet.doGet(IBActionServlet.java:63)
javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:274)
org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:320)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
my.com.kfh.web.utils.IBActionServlet.doGet(IBActionServlet.java:63)
javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
my.com.kfh.web.utils.SetSessionTimeout.doFilter(SetSessionTimeout.java:86)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
java.lang.Thread.run(Thread.java:595)
#2
Updated by Zahir Abd Latif over 8 years ago
- Status changed from Pending Customer Feedback to Closed - End of life cycle
- % Done changed from 0 to 100
Update from chee ping, 8 March 2016 at 17:18;-
Finding:- -Did not found any error or exception in the log file that related to this issue. -Replicate the production instance to development server for testing. No problem found. -Replicate the production instance and the SI record of that customer to development database server for testing. No problem found. I think we can ask customer to clear cache or use different browser to try again.
Will reopen this issue if problem persist.
Issue closed in SCP.