Support #13539
[SCP ID :##6701##] : UNABLE TO DELETE APPROVER (SMART STREAM RESOURCES SDN BHD)
| Status: | Work Completed-End life cycle | Start date: | June 20, 2023 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | IBAM | Spent time: | - | |
| Target version: | - |
Description
Hi Balqis,
Kindly attend below request.
Not able to approve delete approver role at IBAM. [6/20/23 8:57:00:411 SGT] 00000135 SystemOut O 08:57:00.411 [WebContainer : 8] ERROR com.ib.ibss.enterprise.services.ss106_maker_checker.company_user.IBSSAuthorizationResultDeleteCompanyUserServices - Error code : 0000 [6/20/23 8:57:00:411 SGT] 00000135 SystemOut O 08:57:00.411 [WebContainer : 8] ERROR com.ib.ibss.enterprise.services.ss106_maker_checker.company_user.IBSSAuthorizationResultDeleteCompanyUserServices - Error details : null Exception class : com.ib.ibss.enterprise.services.ss123_company_user.ComUserSharedServices, class method : deleteCompanyUser, line number : 102 com.ib.ibss.enterprise.services.ss123_company_user.ComUserSharedServices.deleteCompanyUser(ComUserSharedServices.java:102) com.ib.ibss.enterprise.services.ss106_maker_checker.company_user.IBSSAuthorizationResultDeleteCompanyUserServices.execute(IBSSAuthorizationResultDeleteCompanyUserServices.java:71) com.ib.ibss.controller.actions.ss106_maker_checker.company_user.IBSSAuthorizationResultDeleteCompanyUserAction.execute(IBSSAuthorizationResultDeleteCompanyUserAction.java:79) 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.doPost(ActionServlet.java:525) com.ib.ibss.common.utils.IBSSActionServlet.doPost(IBSSActionServlet.java:81) javax.servlet.http.HttpServlet.service(HttpServlet.java:707) javax.servlet.http.HttpServlet.service(HttpServlet.java:790) com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1235) com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179) com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1134) com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:82) com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:966) com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817) com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:382) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:532) com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:318) com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1833) com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909
History
#1
Updated by Siti Balqis Othman over 1 year ago
- Status changed from New - Begin Life Cycle to System Integration Test
- % Done changed from 0 to 100
Finding:
System unable to retrieve user hard token serial number. Thus, the system throws an exception due to this issue.
According to the user data after confirming with you, this user was not assigned with any token.
Expected Result:
System able to delete user even though it is not assigned with any token.
Solution:
Add Token availability checking before performing the delete process.
Please note, this patch has been deployed to SIT for Bank to perform testing on the given patch.
#2
Updated by Siti Balqis Othman about 1 year ago
- Status changed from System Integration Test to Work Completed-End life cycle
- Assignee changed from Siti Balqis Othman to Zahir Abd Latif
Hi Zahir,
Kindly help to close this ticket. Bank has deployed to production on 20/06/2023.