Time Out error while adding role into GRc cUP request

[Former Member]

Hi

While creating GRC CUP request to add one role, Risk analysis failed due to Time out error.

.I am able to run risk analysis for other user in GRC cUP ..

I did simulation in GRC RAR for this user to add mentioned Role into userid.  It take long time to show the Risk analysis report.But it shows Risk report in GRC RAR.

Error:

Risk analysis failed: Exception in getting the results from the web service :

Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out

Log:

2012-05-21 13:50:41,629 [SAPEngine_Application_Thread[impl:3]_4] 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.jav

a:1161)

    at

com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:38

1)

    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.j

ava:431)

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

    at

com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDisp

atcherImpl.java:321)

    at

com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDis

patcherImpl.java:377)

    at

com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.j

ava: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.ja

va: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.pro

cess(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: 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.RiskAnalysisWS53V1DAO.getViolations(RiskAnalysisWS53V1DAO.java:349)

    at

com.virsa.ae.service.sap.RiskAnalysisWS53V1DAO.getViolations(RiskAnalysisWS53V1DAO.java:457)

    at

com.virsa.ae.service.sap.RiskAnalysisWS53V1DAO.determineRisks(RiskAnalysisWS53V1DAO.java:597

)

    at

com.virsa.ae.service.sap.RiskAnalysis53V1DAO.determineRisks(RiskAnalysis53V1DAO.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.ws53v1.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:

90)

    at

com.virsa.ae.service.sap.ws53v1.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:

99)

    at

com.virsa.ae.service.sap.RiskAnalysisWS53V1DAO.getViolations(RiskAnalysisWS53V1DAO.java:317)

    ... 28 more

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

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

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

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

    at

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

    at

com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:284

)

    at

com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCo

de(HTTPTransport.java:415)

    at

com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessa

ge(MimeHttpBinding.java:563)

    at

com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHt

tpBinding.java:1444)

    at

com.virsa.ae.service.sap.ws53v1.Config1BindingStub.execRiskAnalysis(Config1BindingStub.java:

83)

    ... 30 more

[neerajmanocha · Accepted solution]

Hi Nagaraju,

This usually happens if user has huge violations assigned (violations coming from existing user's roles or coming from new roles assignment).

If user has huge violations, RAR Webservice gets time-out due to long processing for same violations.

Solution is.....

User should be clean before you are going to assign a new role to that user. You can run the risk analysis in RAR for that user and can either remove the access (remover affected roles from user's access) OR mitigate the risks.

Once User is mitigated, you can include mitigation in CUP Risk analysis.

Now this will bring only new violations which are coming due to new role assignment within CUP.

This will avoid time-out issue.

You can refer to SAP Note "1593056 - Best Practices for Remediation of Segregation of Duties risk" for more detail about best practices for remediations.

Thanks & Regards

Neeraj

[neerajmanocha · Accepted solution]

Along with my last reply, also refer to sap note "1696685 - SocketTimeoutException: Read timed out". This is recently released for socket time out issue.

Thanks & Regards

Neeraj

[Former Member]

Hi Nagaraju,

Please ensure that you follow SAP note:

1564243: Risk Analysis Timeout in Compliant User Provisioning

Please make all the settings as described in te above SAP Note.

Also, refer the note 1121978 for more details.

Thanks.

Best regards,

Smriti