try running the PE service out of process, this should at least
stop the crashes. there may still be a bug with a session not
expiring no matter what you return from onSessionExpiringEvent -
i think i remember something like that a while back.
-Chip
[EMAIL PROTECTED] wrote:
>Hi,
>
>My application is using a PAC connected to some legacy.
>I've different data objects for each of the actions I want to perform on the legacy.
>This actions to be performed contains "Log In" and "Log Out" actions.
>The login gives a sessionID in the legacy and the logout sends a command to clear it.
>As you can see, it's quite usual.
>Since users usually forget to click the logout button for explicitly ending a session,
>I'd like it to be done automatically when the ND session expires.
>A good place to place this would be in the onSessionExpiringEvent I suppose.
>Here's the description of one test I've made:
>I've created a small simple project that writes a string from a
>user session object into a file each time a session expires.
>I worked fine but I was very surprised to see that a same session expires
>periodically!!!
>I could add a test to see if a user was alredy logged but it seems that you
>can't read from an expired session (sounds normal in fact) and what would happen
>about performance after 100000 sessions ???
>Even more stange, if there is a problem while getting this event,
>the application server crash an the only way to recover it is to restart NT4.
>More and more strange: even if I remove all the code from inside the caught event,
>ND still crash after one call to the event.
>I've readed things about this event but could someone give me a crear solution to it.
>(and nothing with "java -nojit"... :-)
>
>Thanks,
>
>Serge.
>[EMAIL PROTECTED]
>
_________________________________________________________________________
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]
