[cfaussie] RE: CFMX6.0 Problems

Bruce Trevarthen Thu, 13 Nov 2003 18:39:36 -0800

Title: Message

I had a client who had this trouble. Theirs was CF5. We have experience the same thing on CFMX though.

It turned out to be the datasource connection. We have been able to replicate this easy enough.

If CF has trouble connecting to the database (both instances I refer to were ODBC to MS SQL) it hangs. This is different to removing the database or taking the database server offline, it's a unique situation where MS SQL gets upset and does not talk to CF properly (sorry I don't know the exact detail).

Bruce Trevarthen
Managing Director
-----------------------------------------------------------------
ZeroOne (NZ) Limited
P O Box 9918
Wellington

P: 04-4714444
P: 04-4990018
F: 04-4990019
M: 0275-681695
E: [EMAIL PROTECTED]
W: www.01.co.nz
-----------------------------------------------------------------

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vance Heredia
Sent: Friday, 14 November 2003 2:27 p.m.
To: CFAussie Mailing List
Subject: [cfaussie] RE: CFMX6.0 Problems

There major problem with upgrading to CFMX6.1 is the fact that the same application tends to hang after a few hours of use. There is a single instance of CFMX6.1 running with multiple applications. After a couple of hours the application in question hangs, although all there other applications run just fine.

On Wednesday, Nov 12, 2003, at 21:34 US/Pacific, Vance Heredia wrote:
>> 1)
>> ...Has anyone else created components within the application scope
>> and then found that they have problems when handling complex objects?
>> Are there any solutions.

>CFMX 6.0 has the infamous "page context bug" that can cause problems
>with component instances in shared scopes (although that doesn't
>actually sound like your problem - hard to tell without seeing the
>code). CFMX 6.1 fixes the problem so upgrading would be your solution
>(and you seem to have already confirmed that the problem doesn't occur
>on 6.1).

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 get 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.

>> 2)
>> ...Although once we added the component modules to the 6.0 servers,
>> we began to notice (under load) functions that used to work began
>> stuffing up. ... and variables in the variables/request/client scope
>> are appearing to be mashed and garbled.

>The latter part sounds like the "page context bug". The solution is to
>upgrade to 6.1.

Until we upgrade to 6.1 would creating a dynamic variable to hold this information using time stamps temporarily fix such an error. Eg:

Myvar = "#IP##DateTimeFormat(Now())#";
"To_Enc_#Myvar#_var" = "to_encrypt";
"Seed_#Myvar#_a" = "blah";
"Encrypted_#Myvar#_var" = Encrypt("To_Enc_#Myvar#_var", "Seed_#Myvar#_a");

Would something like this fix this context problem temporarily?

>Any reason why you can't upgrade?

See above ...

Cheers

Vance

>Sean A Corfield -- http://www.corfield.org/blog/

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Vance Heredia

Java Wireless Architect
Global Applications
Lonely Planet Publications
Email: [EMAIL PROTECTED]
Phone: +61 3 8379 8000

http://www.lonelyplanetimages.com/
http://mobile.lonelyplanet.com/
http://wap.lonelyplanet.com/
http://shop.lonelyplanet.com/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---
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.

[cfaussie] RE: CFMX6.0 Problems

Reply via email to