CUP Risk Analysis Error

[former_member771067]

Hi Experts,

OUR GRC AC system configuration is: GRC AC 5.3 CUP Patch 7.0. One of our enduser has requested for a new role through CUP. While the manager performs the risk analysis, it is showing the following error: "Risk Analysis failed: Exception in getting the result from the webservice: service call exception, nested exception is: java.net.socket Timeout Exception: Read timout".

Below is the system log of CUP for futher reference:

2009-12-02 11:08:41,428 [SAPEngine_Application_Thread[impl:3]_12] ERROR com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out com.virsa.ae.core.BOException: Exception in getting the results from the web service : Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199) at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073) at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300) at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109) at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271) 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: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:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: 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 at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:343) at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.getViolations(RiskAnalysisWS53DAO.java:451) at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:569) at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119) at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182) ... 24 more Caused by: 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:311) ... 28 more Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:153) at java.io.BufferedInputStream.fill(BufferedInputStream.java:200) at java.io.BufferedInputStream.read(BufferedInputStream.java:218) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341) at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:553) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432) at com.virsa.ae.service.sap.ws53.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:83) ... 30 more

Could anyone please analyze, where it went wrong.

Thanks a lot in advance.

Regards,

Gurugobinda

[Former Member]

Hi GuruGobinda,

Hope you have maintained the Risk Analysis paramaters properly in CUP --> Configuration --> Risk Analysis

Does the Risk Analysis Web Service URL which you have specified above - works if you call it directly --> it should display an xml output.

Also check the RFC Timeout for Web Services / Background Job Worker Threads (Minutes) in RAR --> Configuration --> Risk Analysis --> Performance Tuning (in our case we have defined it as 1441 minutes).

Thanks

Davinder

[former_member771067]

Hi Davinder,

I have checked the Risk Analysis Web Service URL. It is working fine.The value for RFC Timeout for Web Services / Background Job Worker Threads (Minutes) in RAR: in our case also it has been set to 1441. Not getting exactly where it is getting wrong.

Thanks,

Guru

[koehntopp]

Hi Guru,

is your connector in RAR named exactly the same as in CUP...?

Frank.

[former_member771067]

Hi Frank,

Both the names are same in RAR and CUP.

Thanks,

Guru

[Former Member]

Hi GuruGobinda,

We are facing the exact same issue - And what's more strange is that no changes were mde to RAR / CUP config up until this issue occured..

I've also checked the Configuration Change History in RAR and the Change Log in CUP.

We're on SP09 by the way (with which the Configuration Change Log feature is now included).

Regards,

Lars

[former_member771067]

Hi Lars,

you are right. No changes were mde to RAR / CUP config up until this issue occured. To avoid further delay in approval, we simulated the the user with the new role in RAR and attached the simulation report to the ticket raised by the user.(In RAR, we don't have any issue for this. only in CUP). You can also try with the same, if required.

Thanks,

Guru

[Former Member]

Hi Guru and Lars,

If nothing has been changed. Then look for something that has expired

Like NW license, role assignments and passwords for com users.

regards,

Vit

[s_pados]

We are facing this issue as well. This is seen in requests where there are a lot of conflicting roles requested, or if the user on the backend already has many SoD conflicts.

How many risk violations did show up in the RAR simulation? Seems that above 1000 you will get performance issues in CUP risk analysis.

We are also on SP7 and we did receive a reply from SAP that the risk violation threshold can be changed in RAR as of SP9:

=======================================================

From CUP 5.3 SP9 onwards, we have one parameter in RAR in

'Configuration>Risk Analysis>Performance Tuning' which will

enable you to set threshold violation limit for the Risk Analysis web

service. The name of the attribute is 'Threshold Violation Limit for webservice' and default value of this attribute is 1000.

When you perform risk analysis from CUP and the violation data count

exceeds this limit then error message will appear.

Setting this attribute will help tuning your performance.

==========================================================

Regards,

Stefan.