Based on my testing, the timeout for a session is governed by the ND project that
was requested when the user's session was first created. In this specific example,
the P2PLogin project. No matter what the timeout parameter was for the ECP
project, the timeout parameter for the P2PLogin project took precedence.
However, the project that the user was active in at the time of the timeout was the
project that executed the onSessionTimeoutEvent. If the user was in a P2PLogin
page, that project's onSessionTimeoutEvent was executed. If the user was in an
ECP page, that project's onSessionTimeoutEvent was executed.
Finally, any time the onSessionExpiringEvent was present, regardless of the
project, when the event was executed, java.exe issued an access violation error
(presented via Dr. Watson) and the ND services were automatically restarted. This
remains a mystery to me.
Cheers,
Alan
"Alan Turner" <[EMAIL PROTECTED]> wrote:
>
>We have a system where the following occurs:
>
> 1. User login via ND project P2PLogin
> 2. User selects option that takes them into ND project ECP
> 3. User remains exclusively within ND project ECP for the remainder of the session
>
>If the user's session times out when the user is in project ECP, which project governs
>the timeout processing, ECP where the user timed out or P2PLogin where the session
>ID was initially created?
>
>Thanks,
>
>Alan Turner
>Frito-Lay, Inc.
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
