>
> Subject: RE: CFMX6.0 Problems
> From: Sean A Corfield <[EMAIL PROTECTED]>
> Date: Fri, 14 Nov 2003 14:25:13 -0800
> X-Message-Number: 3
>
> On Nov 13, 2003, at 5:27 PM, Vance Heredia wrote:
> > There major problem with upgrading to CFMX6.1 is the fact
> that the=20
> > same application tends to hang after a few hours of use.
>
> This sounds like a database driver issue. There are tech
> notes on the=20 website about this I think. Check:
> http://www.macromedia.com/support/coldfusion/
Will look into that cheers...
>
> > Hmmm I think I figured out the problem with this (and its
> not 6.0
> > specific anymore as I managed to replicate on the 6.1 servers).
> > I assume that the Result Set object is in a shared memory scope with
> > its reference pointer returned to the user. However if another user
> >hits the same function before the initial user has finished, the
> >initial reference pointer gets over written and becomes redundant as
> > it is replaced by the new pointer causing the initial user to
> > have a read> error, as the object it is referencing is not visible any more.
>
> This sounds extremely unlikely - the query object is created
> on the fly in each request so different users cannot collide (this issue
> came up on another mailing list recently and I confirmed
> with the product team that your supposition is not the case). It must be some other
> issue in your code. I strongly suspect you are not using 'var' to
> declare the query object! You do this:
>
> <cffunction ...>
> <cfset var resultObject = 0/>
> <cfquery name="resultObject" ...
> ...
> </cfquery>
> </cffunction>
>
Hmmm I've had problems declaring variables using the var identifier within function in CFMX6.0. It kept complaining, until I moved it to the top of the component, which didn't serve me with the effect I needed. In CFMX6.1 it appeared to be fine with the var declaration within a the function scope.
> That 'var' declaration is very important. Without it, your
> query is=20 stored as an *instance* variable of the
> component. If your component is in shared scope,
> each call to the function will use the same
> variable, hence the behavior you're seeing.
>
> Sean A Corfield -- http://www.corfield.org/blog/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
______________________________________________________________________ This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not use, copy or disclose its content to anyone. You must not copy or communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner. |
