cancel
Showing results for 
Search instead for 
Did you mean: 

Error while executing Batch Risk Analysis job in full sync mode

Former Member
0 Kudos

Hi Gurus,

I am getting following error while executing Batch Risk Analysis job in full sync mode for the first time, please help me out.

May 12, 2011 3:57:26 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable

INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100

May 12, 2011 3:59:53 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable

INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100

May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchSyncAndAnalysis

INFO: --- Batch Sync/Analysis/Mgmt Report completed --- elapsed time: 104907817 ms

May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob setStatus

INFO: Job ID: 100 Status: Error

May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory

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


2@@Msg is Error Job not completed

May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: -


Background Job History: job id=100, status=2, message=Error Job not completed

May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: -


Complted Job =>100----


May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: Daemon idle time longer than RFC time out, terminating daemon [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0

May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 terminiated

May 12, 2011 4:00:35 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]...

May 12, 2011 4:01:36 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]...

May 12, 2011 4:02:37 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]...

May 12, 2011 4:02:37 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 started

May 12, 2011 4:02:38 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

FINEST: Another Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 is already running

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

I was getting a similar error but resolved it now. The problem was with JCo connections, i had renamed the default names for modeldata & metadata and the connectors were not working. I recreated the connectors with default names and the jobs were executed to completion....Check your JCo connections once.

Former Member
0 Kudos

Hi,

May be it worked in your case How the job names going to affect the execution of the job. The issue is purely because of RFC timeout (As per the logs). I recommend to change the parameter in the configuration tab as recommended by Sunny in the previous thread.

Regards,

Raghu

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Please make sure that configuration parameter "RFC Timeout for Web Services / Background Job Worker Threads (minutes)" in RAR should be set to 1441. Check SAP note 1552118.

Thanks

Sunny