Problem: The application has timed out....

[Andy McMaster]

Hi,

We are getting the following message:

The application has timed out. Please press the browser's refresh key to start again.

The application is being deployed via Citrix. We are pretty sure nothing has changed in our Citrix setup but we are getting this problem intermittently for various users.

Could someone please give me some pointers on what might be causing this or possible lines of enquiry please?

NB. App is not using eBase v4

[Andy McMaster]

Found this info in the Portal:

There is a current bug in Ebase which means this error occurs when a user clicks the browser back button or refresh button, with the Browser Back Button support disabled.

Enabling the browser back button support in Ebase by amending the UFSSetup.properties parameter to "Ufs.browserBackButtonSupport=true" solves the problem.

If the parameter isn't included in the UFSSetup.properties, the default is false. So the parameter (as above) simply needs to be added to the UFSSetup.properties file.

We are using 3.4.0. Build 18092009A

Would this still be an issue or should it have been fixed? I'm pretty sure users are not hitting refresh or back though...

Andy

[ehmd]

If you look under tomcat/conf/web.xml there is a session timeout setting

Code: Select all

    <session-config>
        <session-timeout>30</session-timeout>
    </session-config>

The timeout is a number of minutes and usually defaults to 30 and can be increased. I've had this running at 120 minutes before.

If you are using IIS to serve Ebase, via the Tomcat Connector, you should also look at the documentation as there are a number of Timeout settings on the connector. http://tomcat.apache.org/connectors-doc ... rkers.html. I would also suggest that you upgrade to the latest version of the connector as older versions have caused possible problems around this area.

We run Citrix as well and have not had any problems with Ebase specific to Citrix.

Mark

[Andy McMaster]

Cheers for that.

We have the setting for timeout set to 60 but the error is happening for users sometimes only 5-10 minutes into a session.

We're not using IIS.


Andy