ooops! missed this one yesterday. I have no link to the methodology I mentioned, it
has been discussed here and on CFDJLIST many times though. It involves this:
in application.cfm
<!--- Move Session to Request --->
<cflock timeout="30" throwontimeout="No" type="READONLY" scope="SESSION">
<cfset structappend(request,Duplicate(session))>
</cflock>
in onrequestend.cfm
<!--- move request back to session --->
<cflock timeout="30" throwontimeout="No" type="EXCLUSIVE" scope="SESSION">
<cfset structAppend(session,Duplicate(request))>
</cflock>
With this, our whole application, some 800 templates, uses only two cflocks and no
pcode errors at all. Note, some folks copy the session to request.session, YMMV.
Also note, any use of cflocation in a template may bypass your needed onrequestend.cfm
call, keep this in mind.
Doug
>-----Original Message-----
>From: Andres [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, December 10, 2002 11:04 AM
>To: CF-Talk
>Subject: RE: PCodeRuntimeContextImp::executeSQLTagCFQuery::endTag and
>other weird errors
>
>
>Doug,
>Can you provide a link or location where i can find this methodology?
>
>Thank you!
>
>Andres
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, December 10, 2002 12:49 AM
>To: CF-Talk
>Subject: RE: PCodeRuntimeContextImp::executeSQLTagCFQuery::endTag and
>other weird errors
>
>
>yup, seen that. pcode errors, from what I've experienced and
>from research, are related to one of the most popular topics
>on these lists, locking and shared scopes. We put an app in
>production, after a month or so when it got popular and the
>usage climed, we saw these pcode errors often. We made sure
>every access to session.foo was locked and still got them
>under load, but much less often. Once we changed over to the
>'copy session scope to the request scope' methodology, all the
>pcode errors went bye bye.
>
>
>These makes me wonder...it seems an app can be written in such
>a way as to 'over use' locking/session scope.
>
>
>Doug
>
>>-----Original Message-----
>>From: Andres [mailto:[EMAIL PROTECTED]]
>>Sent: Monday, December 09, 2002 9:31 PM
>>To: CF-Talk
>>Subject: PCodeRuntimeContextImp::executeSQLTagCFQuery::endTag
>and other
>>weird errors
>>
>>
>>Hello All,
>>I have recently (last 36 or so hours) have began experiencing
>>server timeouts, hangs, and have needed to restart CF and IIS
>>in all my servers.
>>
>>Among the many errors i get in the application.log file are
>>things such as
>>PCodeRuntimeContextImp::executeSQLTagCFQuery::endTag and
>>CFTempOnlyForSetVariableNeverUseThisNameInYourCFMLCode122333444
>>455555654321
>>
>>I started a support event with MM. Their engineer tells me it
>>is an issue with shared variable locking. I have began looking
>>closely at my code and have found some potential locking
>>issues. But the fact is that my code HAS NOT CHANGED since we
>>went 5.0 over 5 months ago. No other major changes have taken place.
>>
>>I am starting to make sure all my app, session, and server
>>vars are properly locked, but we host two huge apps (over 1500
>>templates each) so it will take time to go through them.
>>
>>My question is.. has anyone ever experienced their CF server
>>suddenly require such drastic use of cflocking?
>>
>>Any suggestions or ideas will be much appreciated!
>>
>>Thanks
>>
>>Andres
>>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Get the mailserver that powers this list at http://www.coolfusion.com
