Finally, the browser receives the session duration time and sets a timeout to keep the connection alive.
最后，浏览器接收会话持续时间并设置一个超时以保持连接处于活跃状态。
What happens when the WebSEAL proxy session expires because of a timeout or the maximum number of sessions is exceeded?
当由于超时或超出了最大允许的会话数量WebSEAL代理会话超时时，又会如何呢？
Since we were not able to control the session size, we resorted to increasing the available heap space (see the next section) while reducing the session timeout.
由于我们不能控制会话容量，所以我们增大可用的堆空间（见下一部分），同时减少会话超时。
This session timeout also defines how long session state is cached on the server on behalf of a user (WebSphere Application server sets this to 30 minutes by default).
这种会话超时也定义了服务器替用户缓存会话状态的最长时间(WebSphereApplicationServer默认将此设为30分钟)。
Otherwise, the session will persist until it expires, which will consume memory, potentially for a long time, depending on the session expiration timeout.
否则，会话将持久化直到它失效，这会消耗内存，并且可能是长时间的(取决于会话超时时间)。
If you wish to use Aged timeout with JMS connections from within EJBs, ensure that any JMS work is explicitly committed on the JMS session before the EJB method that performs the JMS operations exits.
如果希望将过时超时与ejb中的JMS连接一起使用，则在执行JMS操作的EJB方法退出之前，确保在JMS会话中显式提交任何JMS工作。
If you wish to use Aged timeout with JMS connections from within EJBs, ensure that any JMS work is explicitly committed on the JMS session before the EJB method that performs the JMS operations exits.
如果希望将过时超时与ejb中的JMS连接一起使用，则在执行JMS操作的EJB方法退出之前，确保在JMS会话中显式提交任何JMS工作。
应用推荐