Intermittent error message u201CA timeout error has occurredu201D in InfoView XI3.0

[Former Member]

Hydro One is using an BOE XI 3.0 on IBM AIX 5.3 and Oracle 10.2.0.1 CMS DB with Integration for SAP Solutions. The InfoView, deployed on Tomcat 5.5, is accessed via SAP Enterprise Portal through URL iView. Single Sign-On is achieved by using SAP generated logon ticket to grab user information and trusted authentication mechanism. SAP EP is behind WebSeal Server and https connection has been established between EP, InfoView and WebSEAL. A junction pointing to Tomcat home page (https:// /jsp/common/errorLoading.jsp

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -         ServletPath: /common/appService.do

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -            PathInfo: null

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -            RealPath: /oracle/BOD/sapdata1/H1BOEPILOT/bobje/tomcat/webapps/InfoViewApp/jsp/common/errorLoading.jsp

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -          RequestURI: /InfoViewApp/common/appService.do

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -         QueryString: null

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -      Request Params:

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 actId = 1317

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 errMsg = A timeout error has occurred

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 ctx = standalone

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 pvl = en_US

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 service = error

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 appKind = InfoView

 DEBUG http-8081-Processor23 org.apache.jasper.servlet.JspServlet -                 errStack =

com.businessobjects.webutil.websessiontimeout.WebSessionTimeoutFilter.doFilter(WebSessionTimeoutFilter.java:142)

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)

org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)

org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)

org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)

org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)

org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)

org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)

java.lang.Thread.run(Thread.java:797)

Edited by: Aveek Morshed on Sep 13, 2008 5:16 PM

[Former Member · Accepted solution]

Hi All,

I faced the same issue when I was working on integration project. MY BOBJ Admistrator does as mentioned below:

The general process for extending the web timeouts is as follows:

Go to the following directory:

\BOBJ\BOBJE\Tomcat55\webapps\

(It may be on C:\Program files)

In each of the following Directories there is a WEB-INF directory containing a web.xml file

AnalyticalReporting

CmcApp

CmcAppActions

InfoViewApp

InfoViewAppActions

PartnerPlatformService

PerformanceManagement

PlatformServices

VoyagerClient

Xcelsius

In each case, find the section that contains the following:

<!-- Define the default session timeout for your application,

in minutes. From a servlet or JSP page, you can modify

the timeout for a particular session dynamically by using

HttpSession.getMaxInactiveInterval().

-->

<session-config>

<session-timeout>20</session-timeout> <!-- (some comment) -->

</session-config>

Make a backup copy of the web.xml file and then change the value 20 to 200. Indicate the change in the comment .

After changing all the files, recycle Tomcat.

Regards,

Nisha Makhija

[Former Member]

Did anyone find a fix for this issue? I am facing the same.

[Former Member]

Hi All,

I faced the same issue when I was working on integration project. MY BOBJ Admistrator does as mentioned below:

The general process for extending the web timeouts is as follows:

Go to the following directory:

\BOBJ\BOBJE\Tomcat55\webapps\

(It may be on C:\Program files)

In each of the following Directories there is a WEB-INF directory containing a web.xml file

AnalyticalReporting

CmcApp

CmcAppActions

InfoViewApp

InfoViewAppActions

PartnerPlatformService

PerformanceManagement

PlatformServices

VoyagerClient

Xcelsius

In each case, find the section that contains the following:

<!-- Define the default session timeout for your application,

in minutes. From a servlet or JSP page, you can modify

the timeout for a particular session dynamically by using

HttpSession.getMaxInactiveInterval().

-->

<session-config>

<session-timeout>20</session-timeout> <!-- (some comment) -->

</session-config>

Make a backup copy of the web.xml file and then change the value 20 to 200. Indicate the change in the comment .

After changing all the files, recycle Tomcat.

Regards,

Nisha Makhija

[Former Member]

Hi,

Im facing the same issue. Were you able to find the solution?

[Former Member]

Hi Aveek

Me encountering the same issue at my side.Were you able to resolve it ?

Regards

Kamal