Re: Session Variables Suddenly Stopped Working
Thanks for the suggestion, Dave! We'll give that a try. >From: "Dave Carabetta" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: CF-Talk <[EMAIL PROTECTED]> >Subject: Re: Session Variables Suddenly Stopped Working >Date: Thu, 03 Jun 2004 12:27:56 -0400 > > > >KeAnne, I don't know the answer to your last question, but I'd like to make >a recommendation, if I may, as to your current setup. > >The optimal setup with specific regard to your locking issue would be to >enable the strict locking checkboxes in the CF Administrator in your >*development* environment so as to force the developers to code better, and >then disable the checkboxes in production. The enabling of the features >results in a noticeable performance degradation, particularly under load. >If >you enable the options in your development environment, you force your team >to code smarter and alleviate the need to for overhead in production. > >I use ColdFusion MX now, so I haven't had to worry about this in a while. >But when I was on previous versions of CF, this approach resulted in >noticeable benefits -- 1) your team codes smarter and more proactively, 2) >your production site performance increases, and 3) proper locking will >alleviate the chances of clashes and race conditions, which is why you're >locking in the first place. > >Hope this helps. > >Regards, >Dave. > > > > [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Session Variables Suddenly Stopped Working
>I did talk to the server admin, and she hadn't changed any of the settings >recently, but when I checked the CF Administrator on our test site (which >works), I noticed that the locking information was set differently, so I >changed the lock settings in the production CF Administrator from "Full >Checking" to "No Automatic Checking", and that cleared up the problem >because the code uses the name attribute instead of the scope attribute. > >What I find odd, however, is that this code and the production CF Admin >server settings have not changed in 2 years, meaning that the production >environment has been set to "Full Checking" for a long time, so why did it >suddenly throw the error yesterday? > KeAnne, I don't know the answer to your last question, but I'd like to make a recommendation, if I may, as to your current setup. The optimal setup with specific regard to your locking issue would be to enable the strict locking checkboxes in the CF Administrator in your *development* environment so as to force the developers to code better, and then disable the checkboxes in production. The enabling of the features results in a noticeable performance degradation, particularly under load. If you enable the options in your development environment, you force your team to code smarter and alleviate the need to for overhead in production. I use ColdFusion MX now, so I haven't had to worry about this in a while. But when I was on previous versions of CF, this approach resulted in noticeable benefits -- 1) your team codes smarter and more proactively, 2) your production site performance increases, and 3) proper locking will alleviate the chances of clashes and race conditions, which is why you're locking in the first place. Hope this helps. Regards, Dave. [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Session Variables Suddenly Stopped Working
I did talk to the server admin, and she hadn't changed any of the settings recently, but when I checked the CF Administrator on our test site (which works), I noticed that the locking information was set differently, so I changed the lock settings in the production CF Administrator from "Full Checking" to "No Automatic Checking", and that cleared up the problem because the code uses the name attribute instead of the scope attribute. What I find odd, however, is that this code and the production CF Admin server settings have not changed in 2 years, meaning that the production environment has been set to "Full Checking" for a long time, so why did it suddenly throw the error yesterday? >From: "Deanna Schneider" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: CF-Talk <[EMAIL PROTECTED]> >Subject: Re: Session Variables Suddenly Stopped Working >Date: Thu, 3 Jun 2004 10:36:25 -0500 > >Sounds like the server admins just turned on strict locking validation. >Have >you talked to them? > >- Original Message - >From: "KeAnne Hoeg" > > > The message says "Application.applicationName is in a scope that >contains > > data shared across threads and cannot be accessed without an active >lock". > > > > I know very little about session variables and locking. Does that mean >the > > problem is with the lock itself? > > > > > [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Session Variables Suddenly Stopped Working
Sounds like a change was made from the CF Admin -- a change that now requires you to lock shared scopes. Locking >> Server/Application/Session scope "Full Checking" would do this, I think. If you have to live with this global change in the CF Administrator (shared host, or something), then lock all of your application/session scope reads with read-only locks and lock all of your application/session scope writes with exclusive locks. Same with server scoped vars, though those are fairly unusual. Jamie On Thu, 03 Jun 2004 15:13:56 +, in cf-talk you wrote: >I played with some of the error handling and was able to get a little more >information. > >The message says "Application.applicationName is in a scope that contains >data shared across threads and cannot be accessed without an active lock". > >I know very little about session variables and locking. Does that mean the >problem is with the lock itself? > >>From: KeAnne Hoeg <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>To: CF-Talk <[EMAIL PROTECTED]> >>Subject: Session Variables Suddenly Stopped Working >>Date: Thu, 03 Jun 2004 10:45:57 -0400 >> >>I inherited a site that uses session variables to track users' paths >>through the site and to handle the Admin login section. The code worked >>fine until yesterday when it suddenly stopped working. The only >>information I get is "Processing Error". Does anyone have any idea why it >>suddenly stopped working? One of the admins was able to log in as recently >>as 6/1. >> >>Here's the code in the Application.cfm file: >> >> >> name="solarcenter" >> sessionmanagement="Yes" >> clientmanagement="Yes" >> applicationtimeout=#createTimespan(0,0,90,0)# >> sessiontimeout=#CreateTimespan(0,0,90,0)#> >> >> >> >> type="Exclusive" >> timeout="20" >> throwontimeout="Yes"> >> >> >> >> >> sUserInfo = StructNew(); >> sUserInfo.Address="#CGI.REMOTE_ADDR#"; >> sUserInfo.CFID="#session.cfid#"; >> sUserInfo.Token="#session.cftoken#"; >> sUserInfo.Address="#CGI.REMOTE_ADDR#"; >> sUserInfo.Time="#Now()#"; >> sUserInfo.Template="#CGI.CF_Template_Path#"; >> ID = "#session.cfid##session.cftoken#"; >> >> >>true)> >> >> >> >> > > [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Session Variables Suddenly Stopped Working
You may want to see if the CF Admin set strict locking validation otherwise; I don't really see why you would throw that error off-hand (assuming you are on CF5?) however I would suggest some changes: name="solarcenter" sessionmanagement="Yes" clientmanagement="Yes" applicationtimeout="#createTimespan(0,0,90,0)#" sessiontimeout="#CreateTimespan(0,0,90,0)#"> Move the cfscript out of the application lock since you are dealing only with session variables and create a session lock around them sUserInfo = StructNew(); sUserInfo.Address="#CGI.REMOTE_ADDR#"; sUserInfo.CFID="#session.cfid#"; sUserInfo.Token="#session.cftoken#"; sUserInfo.Address="#CGI.REMOTE_ADDR#"; sUserInfo.Time="#Now()#"; sUserInfo.Template="#CGI.CF_Template_Path#"; ID = "#session.cfid##session.cftoken#"; Try changing from using the variable name #APPLICATION.applicationName# to just the hardcoded name solarcenter and reduce the timeout value: Of course there is always the 'When in doubt - stop/start the CF service' :-) Steve -Original Message----- From: KeAnne Hoeg [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 11:14 AM To: CF-Talk Subject: RE: Session Variables Suddenly Stopped Working I played with some of the error handling and was able to get a little more information. The message says "Application.applicationName is in a scope that contains data shared across threads and cannot be accessed without an active lock". I know very little about session variables and locking. Does that mean the problem is with the lock itself? >From: KeAnne Hoeg <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: CF-Talk <[EMAIL PROTECTED]> >Subject: Session Variables Suddenly Stopped Working >Date: Thu, 03 Jun 2004 10:45:57 -0400 > >I inherited a site that uses session variables to track users' paths >through the site and to handle the Admin login section. The code worked >fine until yesterday when it suddenly stopped working. The only >information I get is "Processing Error". Does anyone have any idea why it >suddenly stopped working? One of the admins was able to log in as recently >as 6/1. > >Here's the code in the Application.cfm file: > > > name="solarcenter" > sessionmanagement="Yes" > clientmanagement="Yes" > applicationtimeout=#createTimespan(0,0,90,0)# > sessiontimeout=#CreateTimespan(0,0,90,0)#> > > > > type="Exclusive" > timeout="20" > throwontimeout="Yes"> > > > > > sUserInfo = StructNew(); > sUserInfo.Address="#CGI.REMOTE_ADDR#"; > sUserInfo.CFID="#session.cfid#"; > sUserInfo.Token="#session.cftoken#"; > sUserInfo.Address="#CGI.REMOTE_ADDR#"; > sUserInfo.Time="#Now()#"; > sUserInfo.Template="#CGI.CF_Template_Path#"; > ID = "#session.cfid##session.cftoken#"; > > >true)> > > > > _ [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
Re: Session Variables Suddenly Stopped Working
Sounds like the server admins just turned on strict locking validation. Have you talked to them? - Original Message - From: "KeAnne Hoeg" > > The message says "Application.applicationName is in a scope that contains > data shared across threads and cannot be accessed without an active lock". > > I know very little about session variables and locking. Does that mean the > problem is with the lock itself? > [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
RE: Session Variables Suddenly Stopped Working
I played with some of the error handling and was able to get a little more information. The message says "Application.applicationName is in a scope that contains data shared across threads and cannot be accessed without an active lock". I know very little about session variables and locking. Does that mean the problem is with the lock itself? >From: KeAnne Hoeg <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: CF-Talk <[EMAIL PROTECTED]> >Subject: Session Variables Suddenly Stopped Working >Date: Thu, 03 Jun 2004 10:45:57 -0400 > >I inherited a site that uses session variables to track users' paths >through the site and to handle the Admin login section. The code worked >fine until yesterday when it suddenly stopped working. The only >information I get is "Processing Error". Does anyone have any idea why it >suddenly stopped working? One of the admins was able to log in as recently >as 6/1. > >Here's the code in the Application.cfm file: > > > name="solarcenter" > sessionmanagement="Yes" > clientmanagement="Yes" > applicationtimeout=#createTimespan(0,0,90,0)# > sessiontimeout=#CreateTimespan(0,0,90,0)#> > > > > type="Exclusive" > timeout="20" > throwontimeout="Yes"> > > > > > sUserInfo = StructNew(); > sUserInfo.Address="#CGI.REMOTE_ADDR#"; > sUserInfo.CFID="#session.cfid#"; > sUserInfo.Token="#session.cftoken#"; > sUserInfo.Address="#CGI.REMOTE_ADDR#"; > sUserInfo.Time="#Now()#"; > sUserInfo.Template="#CGI.CF_Template_Path#"; > ID = "#session.cfid##session.cftoken#"; > > >true)> > > > > [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
