Skip to Content
0
Former Member
Apr 05, 2010 at 08:28 PM

ERM 5.3 Error - READ TIME OUT

34 Views

Hello GRC Community,

<br><br>

I'm running into an issue in GRC 5.3 SP10 for the ERM Module. When we're building a role and get to the risk analysis step, the analysis runs (at the transaction or object level) for a very long time before it kicks back the following error:

<br><br>

<b>Risk analysis failed; Service call exception; nested exception is: java.net.SocketTimeoutException: Read timed out</b>

<br><br>

Here are the system Logs, can someone offer any suggestions as to why we're getting this error?

<br><br>

2010-04-05 15:48:12,548 [SAPEngine_Application_Thread[impl:3]_11] ERROR com.virsa.re.role.actions.RiskAnalysisAction

java.lang.Throwable: Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out<br>

at com.virsa.re.bo.impl.RiskAnalysisBO.performTranLvlRiskAnalysis(RiskAnalysisBO.java:584)<br>

at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystemFromRiskAnalysisPage<br><br>(RiskAnalysisBO.java:167)<br>

at com.virsa.re.role.actions.RiskAnalysisAction.performAndShowRiskAnalysis(RiskAnalysisAction.java:1657)<br>

at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:105)<br>

at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)<br>

at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)<br>

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

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)<br>

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)<br>

at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)<br>

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)<br>

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)<br>

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)<br>

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)<br>

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)<br>

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)<br>

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)<br>

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)<br>

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)<br>

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process<br><br>(ApplicationSessionMessageListener.java:33)<br>

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)<br>

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)<br>

at java.security.AccessController.doPrivileged(Native Method)<br>

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

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

Edited by: suggsda on Apr 5, 2010 10:28 PM