A JVx application has custom timeouts for master and sub session. The timeouts won't work if you use Vaadin UI because a web application uses http session timeout. The Vaadin documentation contains information about Session Timeout After User Inactivity.

Our WebApplicationSetup implementation overrules the session timeout properties of config.xml by setting:

launcher.setParameter("Application.connection.timeout", Boolean.FALSE.toString());
launcher.setParameter("Application.subconnection.timeout", Boolean.FALSE.toString());

If set to false, the timeouts will be set to -1 (infinitly).

This is the default behavior with WebApplicationSetup, but it's also possible to configure custom timeouts for master and sub session by adding the timeout constants:

"Application.connection.timeout"
"Application.subconnection.timeout"

as parameters to the deployment deskriptor (web.xml):

<init-param>
    <param-name>Application.connection.timeout</param-name>
    <!-- 30 minutes -->
    <param-value>30</param-value>
</init-param>