Hi Peter
Basically what happens is:
- A user visits your site & 2 sessions are created (one CF and one J2EE)
- The user goes and has a cup of coffee
- ONE of the sessions times out (because the timeout settings are different)
- The user comes back to her desk and clicks a link
- The timeout of session that is still active gets extended
because of the click
- The other session throws an error
- This user will keep getting this error, while all other users will
have no problems
Using a different browser, changing the application name, restarting
the CF service, etc.. will all temporarily fix the problem because all
the sessions will be reset, but it won't fix the long term problem.
Its a bitch to debug or replicate this one because its only visible
during the window when one session is timed out and the other is still
active.
Anyone using J2EE sessions should search their log files for "session
is invalid" because its very likely that this error is occuring
without you knowing it.
--
Mark Stanton
Gruden Pty Ltd
http://www.gruden.com
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
