>From our experience the following can cause the symptoms you indicated:
1. The inadvertent template containing a <CFINCLUDE> that attempts to
include itself. This falls under the category of "Programmer Head Space and
Timing Errors" - not memory leaks - but quickly consumes all server
resources.
2. An OLEDB and an ODBC Data Source of the same name existing on the server
and templates using <CFQUERY> tags that do not explicitly set the
DBTYPE="OLEDB" (or ODBC). Although the default is supposed to be ODBC, a
single ODBC Call (unset DBTYPE)within an application that is normally
expected to use OLEDB will bring your CF Server Service to its knees. The
opposite could be true if one inadvertently set the DBTYPE to OLEDB in an
instance when the rest of the application is using ODBC. The effect will be
more pronounced if the CF Server is not set to Single Threaded Sessions.
3. Using <!--- ---> to comment out parameters within any CF Tag. The effects
of this can be minimal or vicious depending on exact placement.
4. Corrupted files (CF Templates) on the hard drive. The CF Server cannot
read a file completely and spurious errors occur due to incomplete template
parsing. These may show up as memory leak issues.
5. Outdated MDAC Drivers. The Install package shipped with CF Server is not
the latest and greatest. You can get the latest at
http://www.microsoft.com/data. 2.51 or 2.6 is the latest. Microsoft Access
ODBC drivers for the Web are not recommended as they are single-threaded and
not designed for a mutli-use environment. One bad call to the database by CF
and the rest of the good calls get hung waiting for the thread to clear.
USE OLEDB With Access Databases if you must use Access in the production
environment.
That's all that comes to mind now.
Jim Nitterauer
http://www.creativedata.net
-----Original Message-----
From: Scott Knaub [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 1:44 PM
To: Fusebox
Subject: RE: Memory Leak
When I first recommended CF for our Web site, it got blamed for everything
that went wrong on the Web server. The database administrator and network
administrator used CF for the scapegoat on all issues. We had a memory leak
issue which appeared to be ColdFusion Server (at least the way Windows NT
was showing the allocation of resources). But, after my constant denial that
it was really ColdFusion, we found that the ODBC driver was the culprit and
it was only assigned to ColdFusion because CF was making the calls to the
ODBC driver. We were using an older version of Sybase Adaptive Server
Anywhere. Once we got everything upgraded the memory leaks stopped.
Fusebox and ColdFusion have always stood firm against the attacks from
uninformed administrators.
-----Original Message-----
From: Lee Alder [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 12:17 PM
To: Fusebox
Subject: Memory Leak
Quick question.
I started using fusebox about 6 months ago. Two sites that were done in
fusebox are now being blaimed for memory overload (or leaks). Even thou
these 2 sites get very little in traffic. The system hoasting these sites is
a P2 128 meg, running NT 4.0 (sp 8 I think) and CF 4.5.2 with all service
packs.
IMHO the 'person' saying fusebox is the cause has there head up the fouth
point of contact.
Opinions?
Lee
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
