Using W3@P2200(*WAMONLY) does not clear out all data

Date:20 September 2006
Product/Release:LANSA for the Web
Abstract:Unexpired persistent WAM data does not get cleaned up
Submitted By:LANSA Technical Support

Why doesn't CALL W3@P2200(*WAMONLY) clean out all my data?

According to the guide in section WAM Session Clean Up. There are two settings to keep in mind:

Timeout (minutes) The time in minutes that a session is kept active before it expires. If this time elapses without interaction between the user agent and the server, the session status is updated to expired and the session data is marked as available for cleanup. The default value is 5 minutes.

Cleanup (minutes) The time interval (in minutes) between periodic cleanups performed by the transaction monitor. The cleanup deletes session data of expired sessions. A value of 0 means no cleanup occurs. The default value is 60 minutes.

So the clean up of Web sessions can be done in two ways:

  • via the Transaction Monitor on every 60 mins and will only clean up expired data, as specified by the timeout value default of 5 minutes.
  • directly using CALL W3@P2200 (*WAMONLY), again this will only clean up expired data beyond the 5 mins default.

Keep in mind the Timeout value must be specified with a minimum of 1 minute via the Web Administrator. Otherwise the idea of persistent data does not make sense if the timeout is 0 minutes. So you will always have at minimum under 1 minute of unexpired data that's not cleared.