Hi,

We have a class implementing the ChanelSessionStateChangedListener to
keep track of the session timeout to do some housekeeping tasks. It will
invoke the sessionRemoved method when the timeout interval is reached.
Everything works until we turned on Session persistence in WAS 3.5.6.
The method no longer get invoked even when the specified idle time is
passed. The other functions requring session data works fine thus and
the data seemed to be stored in DB2 sessions table properly.

P.S. We are using WSBCC 4.1.2

Anyone have any ideas?

Regards,

Aaron Chow

[ Post a follow-up to this message ]

To use session persistence, you specify  cookies  true in the dse.ini
channel handler configuration. Then WAS is responsible of  signaling
session expiration events.  WSBCC CSSserver  captures WAS events and
signal  the CSInactivityClientEvent.
You have to configure  WAS:  in the Application Server (usually Default
Server). Select the Services tab, Select Session Manager Service and
click edit properties. Select the Advanced tab, check timeout
radiobutton and specify time in  minutes.


Aaron Chow wrote:
quote:

> Hi,
>
> We have a class implementing the ChanelSessionStateChangedListener to
> keep track of the session timeout to do some housekeeping tasks. It will
> invoke the sessionRemoved method when the timeout interval is reached.
> Everything works until we turned on Session persistence in WAS 3.5.6.
> The method no longer get invoked even when the specified idle time is
> passed. The other functions requring session data works fine thus and
> the data seemed to be stored in DB2 sessions table properly.
>
> P.S. We are using WSBCC 4.1.2
>
> Anyone have any ideas?
>
> Regards,
>
> Aaron Chow
>
>

[ Post a follow-up to this message ]