| >| I had what sounds like the same problem this week.  What database are
you
| >| using?  If it's the same problem (check your server.log file for NT
| >Errors)
| >| then it seems to be caused by ODBC drivers keeping database connections
| >| open.  After the timeout period on the db server, CF tries to use the
same
| >| connection pipe thinking that it's still open, and an error occurs.  I
| >| disabled the 'maintain database connection' option on my oracle odbc
| >driver
| >| and it's now been running fine for about 24 hours (normally it would
hang
| >| after 1-2 hours).

I had this problem some time ago using a Sybase database.  The problem was
that I goofed in my code and one of my queries was taking too long to
complete.  Eventually, it timed out. When the client gave up waiting, it
popped up an error message and stopped.  This left a connection open on  the
server, or left a process running, or something.  When I would look at the
running processes under Task Manager, I would see about 7 - 10 "mtx.exe"'s
running.  If I killed all of these off except for 1 or 2, then the server
would start working again.  If I just left them, the sever appeared to be
locked up.

Seeing as how you say everything works fine on NT4, but not on Win2K, I'm
not sure if this is even remotely similar to what is happening to you.  I am
not at all familiar with Win2K.  I've also never used SQL Server, so I don't
know what this means:

"Error","TID=1448","07/13/00","23:15:58","Unable to write reply -- client
browser stopped waiting for request. "
"Error","TID=1448","07/13/00","23:15:58","Windows NT error number 109
occurred."

but it looks like a runaway query, or a timeout of some sort.

Just my .02 ... I'm probably way off.

Todd Ashworth


------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to