Hello everyone, I am seeing and issue with Lucee 6...
# lucee
s
Hello everyone, I am seeing and issue with Lucee 6 where its ending the session login after 10 minutes of idle time even thought the session time is set to 3 hours in the application.cfc this.sessionTimeout = *CreateTimeSpan*(0, 3, 0, 0). Session vars are stored in a database. On Lucee 5x this is not and issue I have only noticed this when testing Lucee 6. Setting in the admin for Lucee5 and 6 are set the same for scope but Lucee 6 seems to ignore this and after about 10 minutes of idle time it ends the session login. Any ideas? LMK Thanks
e
Under Scopes, change the session type to "JEE" or add it to your cfc,
this.sessionType = "jee";
s
I will give that a try, thanks.
g
It should work regardless of whether you are using an "application/CFML" session type or a java one. if it work with changing the setting to
jee
BUT doesn't work with
cfml
or
application
(they are synonyms for each other) - then I would ask you to create a bug in the Lucee issue tracker. Let us know how you go in your testing!
s
I figured it out. Apparently Lucee 6 does not like a session set as such. session.user = { 'userId': results.userId, 'username': results.username, 'details': user.record() }; I removed that session array and set them as single values and the session scope stays. Very odd!
👍🏼 1
s
That's a bug though, right? We also set session variables in array's plenty of times, works just fine in Lucee 5.x. Hopefully this won't kick is in the butt when we migrate to Lucee 6!
s
It might be. I was only doing this in one application and for some reason it would not keep the session for the time out limit set. I would suggest spinning up Lucee 6 with command box and for yourself.
👍🏼 1
s
We'll be migrating in June, one webapp at a time, so we'll c what we encounter 🙂
s
Yes, please let me know how it works out.