IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Application subsession cleanup

An application subsession is a session within a session. The application subsession also has a context. The toolkit automatically chains this context to the session context so each request running in the application subsession has access to the application subsession context and the session context. An application shares the same session context with the rest of the applications running under this session but each of them has its own application context.

The application subsession context stores only the following three toolkit internal fields:

<kColl id="sessionData" dynamic="false" >
	<field id="dse_sessionId" value="GUFSEDCUGTDHCZHVHNEYGAIXJKFGIRCPFWIOFOFE" />
	<field id="dse_procInfoTable" value="..." />
	<field id="contextTable" value="..."/>
</kColl>	

The dse_sessionId is the application session ID. The other two parameters are for HTML processor management because memory usage related to HTML processors is associated with an application subsession instead of the session.

The application subsession has a freely accessible context for the application to retain any information and service definitions. The application should clean up all of this information when the subapplication session is no longer available. This cleanup can occur as part of the application subsession expiry or as part of a specific application session cleanup occurring during session expiration.

Note that application subsessions are always associated with only one session. When an application session expires, it is the responsibility of the application to perform any needed cleanup for the session and all the application subsessions associated with it. Once an application session has expired, the toolkit treats all its application subsessions as expired also, and no longer checks the application subsessions for timeout. This can cause a problem if an application session expires and the application does not clean up its subsessions, because it means that the application will never be notified of the expiration of those subsessions.

See Managing session for information on how to configure and handle application sessions.



Feedback