Lucee Session Stored in Memory Always?

hacking extensions
1

We’re dumping session data in a Java app via Redis, but its completely empty of actual data:

{hitCount=4, value={"@class":"lucee.runtime.type.scope.storage.IKStorageValue","lastModified":1498152120353,"value":{}}}

The lastModified timestamp does not change however many times I refresh the page and update a session value. Plus, the hit count is off by -1. I strongly suspect Lucee may be still storing session data in memory. I am able to writeDump(session) and all is there as expected in the CFML app, with an incremented hit count that is accurate.

2

I’ve noticed this same behavior but haven’t had a chance to dig into it further yet.

We’re getting around it with sticky sessions at the moment but it’s causing some other challenges and would like to find a resolution for it soon

3

Two things. Firstly, Lucee does store the session data in memory in addition to the cache, but the memory is set to time out very quickly. It’s mostly just keep from going back to the cache for every hit. Secondly, do you have this.sessionCluster set to true? I’m not sure that it would create the scenario you describe, but I’m just curious if it’s affecting it.

4

What version of lucee are you running as there are Jira tickets for 5.2.1.9 to do with Sessions and Clustering…

5

We’re currently on version 4.5.5.006 and I believe it’s been happening for quite awhile. I’m not certain when it first started. I know the session clustering worked with Memcached when we initially deployed the application on Railo in 2014.

I’ve also tested with the Redis extension and it didn’t make a difference.

In App CFC, we’re setting this.sessionCluster = true.

If the user stays on the same server, the session is persisted, however, as soon as you hit a different backend, the session is lost.

6

Just wanted to follow up on this. In our case, we found the issue was with an Application variable this.loginstorage being set to “session”.

After removing this code, sessions and clustering began working again as expected.

7

Hmm, if that’s a bug can you enter a ticket for it please?