cancel
Showing results for 
Search instead for 
Did you mean: 

Error while executing the Job for Objects :null Batch Risk Analysis

Former Member
0 Kudos

Hi All,

We've recently upgraded Virsa to version 5.3_14 . I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles. The job does not complete for some objects and it seems to be sporadic and shows this error: -


Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null

I've attached the log for your review.

Thanks in advance for your help.

Linda Lewis

-


Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>

FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis

WARNING: Job ID:395 : Failed to run Risk Analysis

java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)

at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)

at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)

at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)

at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)

at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)

at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)

at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)

at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)

at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)

at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)

at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:207)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis

WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory

FINEST: --- @@@@@@@@@@@ Updating the Job History -


2@@Msg is Error while executing the Job for Object(s) :ABROWN:null

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: -


Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis

INFO: --- BKG User Permission Analysis (System: P20:020) completed --- elapsed time: 4522 ms

Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock

Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Have you imported teh new messages file?

Regards,

Chinmaya

Former Member
0 Kudos

Yes, we have imported text files. We did correct the function F110S that contained the incorrect authorization object F_REGUL_KOA but this did not resolve the issue.

Former Member
0 Kudos

I would check the function again for any spaces that may have been left in manually correcting it.

regards,

Chinmaya

Former Member
0 Kudos

Hi,

Was a solution found for this error?

Thanks,

Glen