RE: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379)
I was getting a similar error (session is invalid) on an MX6.1/Linux server. The only thing that made it go away was disabling Use J2EE session variables in CF Administrator. I have no idea if that's the actual cause or just a coincidence, but I haven't seen the error since. You should be able to make that error go away by limiting the duration of J2EE session variables within web.xml: http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=10threadid =669435#2598160 Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379)
Thanks Dave! I wonder why they have the web.xml configuration for the timeout set to automatically discover the max timeout set in the administrator. -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 11:51 AM To: CF-Talk Subject: RE: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379) You should be able to make that error go away by limiting the duration of J2EE session variables within web.xml: http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=10 http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=10thr eadid threadid =669435#2598160 Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379)
Don't have. -Original Message- From: Bryan F. Hogan [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 12:03 PM To: CF-Talk Subject: RE: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379) Thanks Dave! I wonder why they have the web.xml configuration for the timeout set to automatically discover the max timeout set in the administrator. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379)
Dave, On 1/9/2004 at 11:51, you wrote: DW You should be able to make that error go away by limiting the DW duration of J2EE session variables within web.xml: DW http://webforums.macromedia.com/coldfusion/messageview.cfm?catid=10threadid DW =669435#2598160 Thanks! I had stopped checking that thread... Are there any specific advantages to using J2EE sessions? Are there any changes to standard CF session code required when changing to J2EE sessions? ~ Ubqtous ~ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: java.lang.IllegalStateException: Session is invalid at jrun.s ervlet.session.JRunSession.checkSessionValidity(JRunSession.java:379)
Are there any specific advantages to using J2EE sessions? Yes, although for most CF developers they probably aren't significant. By default, J2EE session cookies are a bit more obtuse than those used by traditional CF session management, and they're actually session cookies - they don't persist after the browser is closed, for example. You can also use the same session data between CF and JSP/servlet applications using J2EE sessions, and you can take advantage of JRun's clustering if you want to share session data across multiple instances, assuming you're using the full version of JRun. Are there any changes to standard CF session code required when changing to J2EE sessions? Not to my knowledge, as long as your code doesn't refer to CFID or CFTOKEN values directly. You may potentially run into other wacky problems, such as when you redirect to a static HTML page using CFLOCATION and your web server doesn't know how to parse the generated URL with the session token embedded within it. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
