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]
