Solved: CUP Risk Analysis Failed / Read timed out

Hello there,

when I run the risk analysis via CUP for some requests is failed and read Timed Out

I have applied the SAP Note 1564243 SAP Note 1121978 and But that still does not work,

Can you help me ? and do you Have you any suggestions?

Thank you in advance

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Iamiaa,

The issue seems to be because of user is overloaded with the violations that can be be shown in Access controls.

You need to refer: http://service.sap.com/sap/support/notes/1593056

Regards,

Ameet

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello Ameet,

Thank you for your answer,

The problem that for some case,

the request is Create new account and when i simulate the risk in RAR, we just have 3 risks with 1209 Conflicts and it's not work on CUP

and onother case we have one Request Create new Account , and the risk analysis is Run via CUP succeed, the result is we have 3 risks with 1095 Violations

Best Regards,

Lamiaa

Hi Lamiaa,

Which Support pack you are on..?

Ideally there is a threshold with CUP for risk analysis which is around 1000 or so, post this range, CUP starts facing the performance issues.

SAP recommends to go with SP09: There is a parameter in RAR with terma as "Performace tuning" where you can set the threshold of violations limit for RAR, by default it would be set at 1000 and I hope if you change then the issue will be gone.

You can refer: http://service.sap.com/sap/support/notes/1490894

Please check and confirm.

Regards,

Ameet

Message was edited by: Ameet kumar

Hello Ameet,

we are on Support Pack 15.

and the parameter in RAR under Performance Tuning "Web Service Violation limit is set to 0 then there is no upper or lower limit.

I have to set it to a higher value ?

Thank you for your help

Best Regards

Lamiaa

Lamiaa,

what is the message in the system log at the time...?

You will not get anywhere near the issue by guessing parameter values, I'm afraid.

Hello Franck.

The Risk Analysis run in CUP for 15 minutes then i have this message in CUP

Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out

and when i check the Log Message i found this at the time

2014-08-29 09:18:18,838 [SAPEngine_Application_Thread[impl:3]_15] ERROR java.rmi.RemoteException: Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out

java.rmi.RemoteException: Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out

at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:90)

at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:99)

at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:314)

at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:454)

at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:577)

at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)

at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1167)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:381)

at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:118)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)

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

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)

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:1060)

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(Native Method)

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

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

Caused by: java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(SocketInputStream.java:129)

at iaik.security.ssl.Utils.a(Unknown Source)

at iaik.security.ssl.o.b(Unknown Source)

at iaik.security.ssl.o.c(Unknown Source)

at iaik.security.ssl.k.b(Unknown Source)

at iaik.security.ssl.k.a(Unknown Source)

at iaik.security.ssl.k.read(Unknown Source)

at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)

at java.io.BufferedInputStream.read(BufferedInputStream.java:201)

at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:904)

at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:383)

at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:292)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:421)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:563)

at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1447)

at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83)

... 30 more

2014-08-29 09:18:18,841 [SAPEngine_Application_Thread[impl:3]_15] DEBUG RiskAnalysisBO.java@197:findViolations() : RiskAnalysis___ Failed with Exception : Exception in getting the results from the web service : Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out

2014-08-29 09:18:18,841 [SAPEngine_Application_Thread[impl:3]_15] DEBUG com.virsa.ae.service.ServiceException: Exception in getting the results from the web service : Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out

Hi Lamiaa,

anything in the RAR logs on why it won't come back...?

Frank,

The message i get in RAR Log's is :

Aug 29, 2014 10:04:17 AM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=35000 memory changed=109M, free=824M, total=1948M, time spent skip:193ms, total: 1569ms

Hi Lamiaa,

Set Web Service Violation limit to a higher limit.

And if you refer the note: http://service.sap.com/sap/support/notes/1490894

Then you would get to understand the other way out to resolve this issue. Like to check for the existing violations if its coming from SAP* profiles and others.

Do refer to the note 1490894

Regards,

Ameet

Hello,

We have a Cross system, and i think that this what impact CUP analysis Performance.

Do you have any idea about this ?

Thank you in advance

Lamiaa

Hi Lamiaa,

You are running the risk violation reports across cross systems or on just a particular syste.?

Will not mattrr anyways if you set the parameter to a higher limits..like i mentioned in ny previous post.

Did you raise the limit.?

Raising limit will definitely help in overcoming this issue and check for the users authorizations if it contains any SAP profiles.

Regards,

Ameet

Hello Ameet,

Thank you very much for your answer,

I raise the parameter to a higher value, but i think that this is not the problem .

in the logs we have INFO: performActPermAnalysis completed ,

But i dont understand this line

Oct 15, 2014 7:11:00 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-567M, free=1299M, total=1948M, time spent skip:0ms, total: 24464ms?

I think i have to raise onother parameter but i dont know wich one?

Thank you for your help !

FINEST: Lock:1002

Oct 15, 2014 7:09:26 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS getNewJob

FINEST: New job ID:1089, file:.tmp_IWS1089

Oct 15, 2014 7:09:26 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1002

Oct 15, 2014 7:09:26 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Analysis Daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. processing Web Service Call ID:1089

Oct 15, 2014 7:09:27 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : Before Rules loading, elapsed time: 33 ms

Oct 15, 2014 7:09:27 PM com.virsa.cc.xsys.util.RuleLoader getActRuleMatrix

INFO: No of Systems=3

Oct 15, 2014 7:09:27 PM com.virsa.cc.xsys.util.Lock lock

WARNING: It is used by the same owner: For current thread retrying to get lock : 1002

Oct 15, 2014 7:09:27 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1002

Oct 15, 2014 7:09:27 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1002

Oct 15, 2014 7:09:31 PM com.virsa.cc.xsys.util.RuleLoader getActRuleMatrix

INFO: Action rules cache loaded: memory used in cache=-339M, free=1137M, total=1948M

Oct 15, 2014 7:09:31 PM com.virsa.cc.xsys.util.RuleLoader getActionRules

FINEST: Rule Loader Rules Size=>24774

Oct 15, 2014 7:09:31 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : Rules loaded, elapsed time: 4738 ms

Oct 15, 2014 7:09:31 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : # objects to analyse: 1

Oct 15, 2014 7:09:31 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : Analysis starts: TEST_CROSS

Oct 15, 2014 7:09:32 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>

FINEST: ObjAuthMatcher constructed: 2ms, #singles=1074, #ranges=0, #super=0

Oct 15, 2014 7:09:32 PM com.virsa.cc.dataextractor.bo.DataExtractorSAPJCO getObjPermissions

FINEST: getObjPermissions: elapsed time=129ms

Oct 15, 2014 7:09:32 PM com.virsa.cc.dataextractor.bo.DataExtractorSAPJCO getObjPermissions

FINEST: getObjPermissions: elapsed time=92ms

Oct 15, 2014 7:09:32 PM com.virsa.cc.dataextractor.bo.DataExtractorSAPJCO getObjPermissions

FINEST: getObjPermissions: elapsed time=200ms

Oct 15, 2014 7:09:34 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>

FINEST: ObjAuthMatcher constructed: 8ms, #singles=3215, #ranges=0, #super=0

Oct 15, 2014 7:09:38 PM com.virsa.cc.dataextractor.bo.DataExtractorSAPJCO getObjPermissions

FINEST: getObjPermissions: elapsed time=4411ms

Oct 15, 2014 7:10:16 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : Analysis done: TEST_CROSS elapsed time: 45135 ms

Oct 15, 2014 7:10:16 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : 1 out of 1 (100%) done

Oct 15, 2014 7:10:16 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Foreground : All Analysis done, elapsed time: 49914 ms , memory usage: free=826M, total=1948M

Oct 15, 2014 7:10:16 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

INFO: Detailed Analysis Time:

Risk Analysis Time: Started @:Wed Oct 15 19:09:26 CEST 2014

Rule Load Time: Started @:Wed Oct 15 19:09:27 CEST 2014

Rule Load Time:4739millisec

Org Rule Loop Time: Started @:Wed Oct 15 19:09:31 CEST 2014

Rule Loop Time: Started @:Wed Oct 15 19:09:31 CEST 2014

Rule Loop Time:45093millisec

Org Rule Loop Time:45093millisec

Risk Analysis Time:49950millisec

Oct 15, 2014 7:10:16 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysisRE

INFO: performActPermAnalysis completed ...

Oct 15, 2014 7:10:22 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=18M, free=792M, total=1948M, time spent skip:2ms, total: 4920ms

Oct 15, 2014 7:10:27 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-18M, free=810M, total=1948M, time spent skip:966ms, total: 5211ms

Oct 15, 2014 7:10:33 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-8M, free=795M, total=1948M, time spent skip:1212ms, total: 5320ms

Oct 15, 2014 7:10:36 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=7808 memory changed=32M, free=739M, total=1948M, time spent skip:1888ms, total: 2152ms

Oct 15, 2014 7:10:36 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=4692 memory changed=7M, free=732M, total=1948M, time spent skip:71ms, total: 226ms

Oct 15, 2014 7:11:00 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-567M, free=1299M, total=1948M, time spent skip:0ms, total: 24464ms

Oct 15, 2014 7:36:44 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Daemon idle time longer than RFC time out, terminating daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/.

Oct 15, 2014 7:36:44 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: Daemon idle time longer than RFC time out, terminating daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 2

Oct 15, 2014 7:36:44 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 6 terminiated

Oct 15, 2014 7:36:44 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 2 terminiated

Oct 15, 2014 7:36:44 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

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

Oct 15, 2014 7:36:44 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 0 terminiated

Oct 15, 2014 7:36:45 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Daemon idle time longer than RFC time out, terminating daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/.

Oct 15, 2014 7:36:45 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 4 terminiated

Oct 15, 2014 7:36:45 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: Daemon idle time longer than RFC time out, terminating daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 1

Oct 15, 2014 7:36:45 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 1 terminiated

Oct 15, 2014 7:36:45 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Daemon idle time longer than RFC time out, terminating daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/.

Oct 15, 2014 7:36:46 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 3 terminiated

Oct 15, 2014 7:36:46 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Daemon idle time longer than RFC time out, terminating daemon [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/.

Oct 15, 2014 7:36:46 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 7 terminiated

Oct 15, 2014 7:37:01 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:02 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:02 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 0 started

Oct 15, 2014 7:37:02 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 1 started

Oct 15, 2014 7:37:03 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:03 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start

INFO: Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 2 started

Oct 15, 2014 7:37:04 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:04 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 3 started

Oct 15, 2014 7:37:05 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:05 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 4 started

Oct 15, 2014 7:37:06 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:06 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 6 started

Oct 15, 2014 7:37:07 PM com.virsa.cc.xsys.bg.AnalysisDaemonThread run

FINEST: Analysis Daemon Thread: Invoking (HTTPS): https://starscmx.sanofi-aventis.com:50001/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daem...

Oct 15, 2014 7:37:07 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonWS start

INFO: WS Analysis Daemon ID [2309650]/usr/sap/CMX/JC00/j2ee/cluster/server0/. Thread ID 7 started

Oct 15, 2014 7:37:28 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=1M, free=1012M, total=1948M, time spent skip:910ms, total: 5730ms

Regards;

Lamiaa

Hi Lamiaa,

Confirm a few things:

You are running risk violation reports on user level specific to a particular system or cross system..?

Check for this user authorization to all the systems if it contains any SAP* profiles.

In case, where the violations are numerous, similar issue comes in the picture and let to the timeout sessions.

You need to contact the Basis team to enhance the time-out sessions as well. This limit can also have some dependency.

Regards,

Ameet

Hello Ameet,

WE are running risk violation on CUP Risk Analysis Online , in Cross system

When i simulate a risk analysis in RAR i have the Result 13 Riskswith 4692 conflits.

But in CUP i have Risk Analysis Failed.

The user don't have SAP* Profiles but he had Roles with a some risks, But we can't remediate these users.

The basis team ? for cheking what exactly ?

Thank you so much for your help

Hi Lamiaa,

It could be due to the issue with RTA's or JACO; connectors between your GRC system to the satellite system.

Obviously, as long as RAR will not be able to bring up all the associated violations, CUP will be going into timeout sessions.

Have you configured the service levels for the request types under configuration tab..?


lamiaa kharmich wrote:

Oct 15, 2014 7:11:00 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines
FINEST: readSpoolReportLines done, lines read=100000 memory changed=-567M, free=1299M, total=1948M, time spent skip:0ms, total: 24464ms?

This clearly indicates the unavailability of the required memory space to support the risk violation reports.

You need to contact BASIS or DBA team to get this space enhanced.

Hope this should help now.

Regards,

Ameet

Hello Armeet.

Thank you very much for your help.

How can we configure the service level for the request ?

Because we don't have any service level configured.

And do you know any parameter we have to modify by the basis team ?

Thank you in advance

Regards,

Lamiaa

Hi Lamiaa,

At this moment, I am not able to recall from the top of my head on how to configure the service levels. It's been long time since i worked with AC 5.3

As far as remember, you have to try to uncheck the option "Perform risk analysis on request" under configuration tab.

One more question: Do you have the risk analysis set to get performed at access request creation stage, configured in the configuration settings..?

You need to uncheck that under the configuration -> risk analysis area. And also, what type of roles request are you creating for this user? Perhaps your roles might have too many SOD violations or the userid that you're creating the request for might have too many SOD Risks that the RAR analysis is timing out.

You can refer below links on how to configure service levels:

Access Requests and Service Levels - SAP GRC Access Control 5.3 (AC) - SAP Library

GRC AE: Service Levels - SAP GRC Access Control 5.3 (AC) - SAP Library

Hope this address your final concern.

Let us know for any more help.

Regards,

Ameet

Hello Ameet,

Thank you very much for your help.

we dont activate the option "Perform risk analysis on request" under configuration tab.

we don't have the risk analysis set to get performed at access request creation stage.

yes for cross system ; users and rôles has some violation but it's just 13 Risks with 4692 conflits.

i compare the log of one risk analysis CUP with 9 risks for 1 backend and onother with 13 risks on Cross system.

The only thing i see in RAR logs, is this , but the memory is still free we have for example 212 M free.

but time spent skip : 0 ms???

Rule Loop Time:491604millisec

Org Rule Loop Time:491604millisec

Risk Analysis Time:497890millisec

Oct 16, 2014 6:00:05 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysisRE

INFO: performActPermAnalysis completed ...

Oct 16, 2014 6:00:55 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=81M, free=28M, total=1948M, time spent skip:1ms, total: 49811ms

Oct 16, 2014 6:01:44 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-141M, free=170M, total=1948M, time spent skip:892ms, total: 49113ms

Oct 16, 2014 6:02:35 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-60M, free=207M, total=1948M, time spent skip:1816ms, total: 50219ms

Oct 16, 2014 6:02:40 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=7808 memory changed=34M, free=150M, total=1948M, time spent skip:1804ms, total: 2049ms

Oct 16, 2014 6:02:40 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=4692 memory changed=9M, free=141M, total=1948M, time spent skip:1ms, total: 76ms

Oct 16, 2014 6:03:20 PM com.virsa.cc.xsys.riskanalysis.dao.dto.RAReportDTO readSpoolReportLines

FINEST: readSpoolReportLines done, lines read=100000 memory changed=-70M, free=212M, total=1948M, time spent skip:0ms, total: 40250ms

Thank you

Lamiaa

Hi Lamiaa,

Could you pelase enhance the memory space and see if that rectifies your current issues..

Did you contact your DBA or BASIS team with this error log.

Yes, you are right about the available free space at 212 M, but guess it might need further addition to execute reports.

I can say that this should be resolved with little bit of help from DBA or BASIS team, this is not occuring due to any configurations with GRC box.

Regards,

Ameet

Hi Lamiaa,

Where you are at this issue?

How about if you close this thread or let us know if you still haven't got the solutions.

Regards,

Ameet

Hello Ameet,

We raised the Heap Size from 2048 to 2560.

But we still have the same error when running Risk Analysis in CUP :

{

Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out

}

From the server side those are the errors we have :

{

#1.#06E0562B8BF90022000004E300005B3E00050690911818B7#1414592862883#com.virsa.ae.commons.utils.Util#sap.com/grc~aeear#com.virsa.ae.commons.utils.Util#E0199058#64##n/a##50127f635f7711e49252000000233e12#SAPEngine_Application_Thread[impl:3]_22##0#0#Error#1#/Applications/AccessEnforcer#Java###Date format Error

[EXCEPTION]

#1.#06E0562B8BF9002200000F2800005B3E00050690AA0132E0#1414593280812#/Applications/AccessEnforcer#sap.com/grc~aeear#com.virsa.ae.commons.AELogger#E0199058#64##n/a##50127f635f7711e49252000000233e12#SAPEngine_Application_Thread[impl:3]_22##0#0#Warning#1#com.virsa.ae.commons.AELogger#Plain### Util.java@1162:parseInt() : Ignoring null, setting to default value : 0#

#1.#06E0562B8BF9002200000F2900005B3E00050690AA0337D1#1414593280945#/Applications/AccessEnforcer#sap.com/grc~aeear#com.virsa.ae.commons.AELogger#E0199058#64##n/a##50127f635f7711e49252000000233e12#SAPEngine_Application_Thread[impl:3]_22##0#0#Warning#1#com.virsa.ae.commons.AELogger#Plain### Util.java@1162:parseInt() : Ignoring null, setting to default value : 0#

#1.#06E0562B8BF900300000027900005B3E00050690BE0025F1#1414593616287#System.err#sap.com/tc~wd~dispwda#System.err#FRX24368#67##n/a##224259555f7911e48b3f000000233e12#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Oct 29, 2014 3:40:16 PM com.virsa.cc.common.RiskAnalysisReport render

INFO: RiskAnalysisReport render: memory changed=-357M,free=1534M, total=2460M

1.#06E0562B8BF9002D0000000300005B3E00050690C0C7FB59#1414593662940#System.err#sap.com/tc~wd~dispwda#System.err#FRX24368#67##n/a##224259555f7911e48b3f000000233e12#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Oct 29, 2014 3:41:02 PM com.virsa.cc.common.RiskAnalysisReport render

INFO: RiskAnalysisReport render: memory changed=0M,free=1522M, total=2460M

}

Do you have any ideas about those errors ?

Especially the fact that we are having "memory changed=-357M " while we changed the Memory Heap Size ?

Thank you

Jamal (Lamiaa's backup)

Hi Jamal,

Sorry for late reply.

How long does it take to get you the risk reports.?

It's happening due to the mass number of associated risks.

You can either minimise the risks by checking for sap* profiles. Or if not then raising this message to SAP should be your next move.

Regards,

Ameet

Hi Ameet,

I really appreciate your help.

It takes 30 minutes which is the "maximum time to wait" set in RAR configuration.

We upgraded our Java Servers and added a new node.

Which doubles the memory capacity.

Now we have 4 GO of memory but it didn't solve the issue.

A negative value still shows in the memory changed parameter.

We are looking for another memory / buffer parameter to change.

We also found that our JCOs for HR are not created and were unable to create them due to a server name error in SLD (it might be the cause of our issue).

We'll keep searching for now.

Thank you !

Jamal

Hi Jamal,

That's really a very long time before system throws a run time error.

You were running risk reports for the users available in what system..is that HR?

As you mentioend, JCo is still not yet established between GRC and HR system, are you able to see this HR system under the search criteria before you run the reports?

Test the connectivity betwen HR to GRC, you can hit "ping"meta data and model to see if this is in place.

But, in case you are encountering with the issue while risk reports generation for some other backend connector and not HR, I would suggest to run the connectivity test for that connector and if this is working fine then it could cause due to some bug. Clearly memory is not creating the issue now.

Regards,

Ameet

Hi Kumar,

Just for your information, we still didn't solve this issue.

We contacted SAP Support and are waiting for their response.

If we ever find a solution. I'll make sure to post it here.

Thank you Kumar !

Best regards,

Jamal HALAQ

Answers (1)

Hard to answer with that little information - what does the system log say?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This message was moderated.

Ask a Question

CUP Risk Analysis Failed / Read timed out

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)

Re: ASEGURAMIENTO DE TABLAS

Re: Getting error while Creating role in BRM

Re: How to enable the add, delete,edit system on s...

Re: CJS-30252 Running priviledged function stop of...

Successfactors login issue.