Yes, 20 mins is probably the case - if they had it set up correctly (max in the admin = max in the J2EE conf) the error wouldn't appear at all...
-----Original Message----- From: Sean Corfield [mailto:[EMAIL PROTECTED] Sent: Monday, 14 February 2005 9:31 To: CF-Talk Subject: Re: Why would Firefox cause CF to error?? They need to check the underlying J2EE session timeout to ensure it really is the same as the maximum session timeout they're allowing for CF's sessions. I'm pretty sure the default JRun timeout is 20 minutes, not 30 (but I may be misremembering). Are you setting the session timeout in your app longer than 30 minutes? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:194490 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
