We are setting up a new production environment using Lucee. We are running
2 instances behind a load balancer in a round robin configuration.
First thing we are noticing is that when logging into our app on 1 instance
and redirecting during the sign in process if we land on the 2nd instance
the client variables are not populated. We store the client variable in a
database.
In our testing we noticed that deleting the client variables from the
database and refreshing the page actual re-created all the variables with
out going through the sign in process again. So our theory is that client
variables are cached in Lucee’s Memory and then stored in the database
after some time. We also tested deleting all variables from the database
and restarting the instance to verify that client variables are store in
memory and that Lucee does not verify that they are in the database.
My Question is:
Does Lucee cache client variable in memory and them dump to the database?
If there is a delay in the save to the database how would you persist
client data to multiple instances on a larger scale?
Be careful with : it happened to me a lot that the session info was not written to the database yet, when the Location-change occured. This sucked when doing a login routine with sessions vars, with a follow-up cflocation.
Does Lucee cache client variable in memory and them dump to the database?
By default, yes. Option 1) above will fix that.
Kind regards,
Paul KlinkenbergOp 7 aug. 2015, om 01:17 heeft Ken John <@Ken_John> het volgende geschreven:
Hello,
We are setting up a new production environment using Lucee. We are running 2 instances behind a load balancer in a round robin configuration.
First thing we are noticing is that when logging into our app on 1 instance and redirecting during the sign in process if we land on the 2nd instance the client variables are not populated. We store the client variable in a database.
In our testing we noticed that deleting the client variables from the database and refreshing the page actual re-created all the variables with out going through the sign in process again. So our theory is that client variables are cached in Lucee’s Memory and then stored in the database after some time. We also tested deleting all variables from the database and restarting the instance to verify that client variables are store in memory and that Lucee does not verify that they are in the database.
My Question is:
Does Lucee cache client variable in memory and them dump to the database?
If there is a delay in the save to the database how would you persist client data to multiple instances on a larger scale?
Be careful with : it happened to me a lot that the session
info was not written to the database yet, when the Location-change occured.
This sucked when doing a login routine with sessions vars, with a follow-up
cflocation.
Does Lucee cache client variable in memory and them dump to the
database?
By default, yes. Option 1) above will fix that.
We are setting up a new production environment using Lucee. We are
running 2 instances behind a load balancer in a round robin configuration.
First thing we are noticing is that when logging into our app on 1
instance and redirecting during the sign in process if we land on the 2nd
instance the client variables are not populated. We store the client
variable in a database.
In our testing we noticed that deleting the client variables from the
database and refreshing the page actual re-created all the variables with
out going through the sign in process again. So our theory is that client
variables are cached in Lucee’s Memory and then stored in the database
after some time. We also tested deleting all variables from the database
and restarting the instance to verify that client variables are store in
memory and that Lucee does not verify that they are in the database.
My Question is:
Does Lucee cache client variable in memory and them dump to the database?
If there is a delay in the save to the database how would you persist
client data to multiple instances on a larger scale?
-Ken
–
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get your
ticket NOW - http://www.cfcamp.org/