- SAP Community
- Products and Technology
- Additional Q&A
- RAR 5.3 Background Syncs - Java errors
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
RAR 5.3 Background Syncs - Java errors
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 06-21-2010 9:58 PM
Hi!
We are upgrading from CC 5.2 to RAR 5.3 SP11:
1) When running the background Sync or user risk analysis job, there are java messages appearing in the job log. The background job will complete. And it seems to run successfully.
Are the java messages normal or is this an error?
Partial messages from log:
Jun 21, 2010 7:58:17 AM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForRoleInputElement.wdGetObject(IPublicBackendAccessInterface.java)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.executeBAPI(InternalBackendAccessInterface.java:4696)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:213)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:105)
at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:813)
at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:121)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1355)
at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:311)
2) Viewing the parameters of a background job for Full Syncs, what is batch mode: INC? I noticed this is new for RAR 5.3.
Task: Risk Analysis - Batch
Name: Full: All Syncs for AC3 only
Field Name Field Value
ROLE_SYNC: AC3
BATCH_MODE: INC
LANG: EN
USER_SYNC: AC3
SYNC_MODE: FULL
PROF_SYNC: AC3
Thank you,
Lynn
Accepted Solutions (0)
Answers (5)
Answers (5)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Note 1562775 - java.lang.NullPointerException in the RAR logs
Summary
Symptom
" SEVERE: null
java.lang.NullPointerException" error is coming in the logs.
Other terms
RAR, NullPointerException, SAPJCO, JCO, Adaptive RFC.
Reason and Prerequisites
"SEVERE: null
java.lang.NullPointerException
at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForUserInputElement.wdGetObject(IPublicBackendAccessInterface.java)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)"
The above mentioned error may come because the connector for which job has been run is of Type JCO.
Solution
As a workaround to avoid this error in the logs, change the Connector Type of the connector for which you are running the background job from Adaptive RFC type to SAPJCO.
Now restart the J2EE server and again schedule the job.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Lynn,
We are experiencing the same issue. We are on SP11 aswell.
Initially we had problem with ORA exceptions 18 and 604. SAP Support suggested to increase the sessions parameter in the database. With that the problem got resolved, but now we are getting this error.
The analyse seems to work, but it generates loads of junk in the error log.
Did you ever resolved this?
Kind regards,
Vit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello,
Our SAP adapter is inactive. We are not using Risk Terminator.
Our connectors are fine.
Regards,
Lynn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Lynn,
After upgrading from 5.2 to 5.3 SP11, did you do the following:
1. If you are using the Adapter type of connector and if inactive, activate it by clicking the grey diamond? The status should turn green.
2. Upgrade your RTA to the corresponding versions (e.g. AC5.3 SP11 = VIRSANH 11; VIRSAHR 10)?
3. Reboot your entire GRC application and database after the upgrade?
-Dylan
P.S. I forgot to add in earlier that you can change the logger style too. Configuration --> Miscellaneous --> Default Logger Parameter.
Edited by: Dylan Hack on Jun 30, 2010 3:01 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Dylan,
Yes, we have already performed the items you mentioned. Thanks.
Sunny might have trigger us to review the SAP Adapter. We do not use Risk Terminator (RT).
But our front end (connectors) is configured for RT. But our backend is not.
So we think it might be trying to read the backend (SAP). Giving us a bunch of java messages/errors.
We think this is the problem. And plan to ignore the java messages on the log.
Thanks.
Lynn
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Sunny,
Thank you for the reply back.
I am re-ran the Full Sync for Users. But the java errors still appear.
Beginning of the job log:
INFO: -
Scheduling Job =>923----
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BgJob run
INFO: --- Starting Job ID:923 (RISK_ANALYSIS_BATCH) - Full: Sync for User for AC3 only
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 923 Status: Running
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BgJob findJobHistory
FINEST: --- @@@@@@@@@@@ Find the Job History -
1
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
1@@Msg is Full: Sync for User for AC3 only started :threadid: 0
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
Background Job History: job id=923, status=1, message=Full: Sync for User for AC3 only started :threadid: 0
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchSyncAndAnalysis
INFO: --- Batch Sync/Analysis/Mgmt Report started ---
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
INFO: @@@ User sync params true: Syskey List is [AC3]
Jun 22, 2010 7:49:48 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
INFO: Started User sync for System AC3###true
Jun 22, 2010 7:49:48 AM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IUserListInputElement.wdGetObject(IPublicBackendAccessInterface.java)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
at com.virsa.cc.comp.BackendAccessInterface.searchUser(BackendAccessInterface.java:761)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.searchUser(InternalBackendAccessInterface.java:4279)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.searchUser(InternalBackendAccessInterface.java:4748)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchObj(DataExtractorSAP.java:381)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.loadUserData(BatchRiskAnalysis.java:366)
at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1288)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:529)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:339)
Middle of the job log: I noticed that everytime it grabs the next bapi user ranges the java error appears.
INFO: User Sync Insert BAPI User data for SysKey:AC3#masterSys:AC3#from:10006137#to:10012300# fullscan is true
Jun 22, 2010 7:50:09 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis getBAPIUserData
INFO: --- Data Extractor -
com.virsa.cc.dataextractor.bo.DataExtractorSAP@3c6c3c6c
Jun 22, 2010 7:50:09 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis getBAPIUserData
INFO: -- Last Run Date is 1970-01-01
Jun 22, 2010 7:50:09 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis getBAPIUserData
INFO: -- Current Date is 2010-06-22
Jun 22, 2010 7:50:09 AM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: null
java.lang.NullPointerException
at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthChgUserInputElement.wdGetObject(IPublicBackendAccessInterface.java)
at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
2) Regarding the parameters, why is there be an INC - incremental batch mode if I am running a FULL User/Role/Profile Synchronization job?
Thanks.
Lynn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
1) For Error you are getting in job- Is SAP Adapter working ?
2) Incremental Batch Risk Analysis is an option which SAP has given. Once you will run Full sync, Full batch Risk analysis and Management Report. Then you can schedule incremental Sync and incremental Batch Risk analysis job daily to keep RAR in sysnc with your backend system.
Thanks
Sunny
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
> java.lang.NullPointerException
> at >com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForRoleInputElement.wdGetObject(IPublicBackendAccessInte>rface.java)
> at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
> at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:401)
> at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
Check below link for this:
>
> 2) Viewing the parameters of a background job for Full Syncs, what is batch mode: INC? I noticed this is new for RAR 5.3.
> Task: Risk Analysis - Batch
> Name: Full: All Syncs for AC3 only
>
> Field Name Field Value
> ROLE_SYNC: AC3
> BATCH_MODE: INC
> LANG: EN
> USER_SYNC: AC3
> SYNC_MODE: FULL
> PROF_SYNC: AC3
Batch Mode:INC means Incremental Batch Risk Analysis.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- How to troubleshoot BusinessObjects Business Intelligence Platform server/service issues in Technology Blogs by SAP
- Users are not getting synced to IAS from SAP SF- The SSL certificate error in Human Capital Management Q&A
- Advance Return Management complete configuration(SAP ARM) in Enterprise Resource Planning Blogs by Members
- Unify your process and task mining insights: How SAP UEM by Knoa integrates with SAP Signavio in Technology Blogs by SAP
- ABAP Matrix (AFM/ALM) in Technology Blogs by Members
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.