RE: cfmx - request timeout setting

[Gaulin, Mark]

Can you use cflock with a timeout around access to this table?  (Have the purge get an exclusive lock and all readers get a read only lock with a 10 or 30 second timeout.)  This could be a purely logical lock too... it doesn't need to literaly surounding the database table accesses, so if you wanted the entire web site to be "off" during the purge then you could put the cflock for read in application.cfm... if you can get the lock, even for a moment, then all is well, otherwise cfabort the page.


    Mark

-----Original Message-----
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 05, 2004 10:38 AM
To: CF-Talk
Subject: Re: cfmx - request timeout setting

heres the problem:

we have 29 million row database, that purges about 380000 rows each
morning @ 3:00 am.

if requests to that database are made during that deletion, in about
10 - 15 minutes, we lose the cfmx server.  i can reproduce 100 times
over, so i know its the problem.  i have the time out set to 30
seconds, in the admin, as well as the jrun.xml.

what can i do about this?

thanks.
tony

On Thu, 05 Aug 2004 14:30:05 +0000, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> You can't kill it.  In CF5 and earlier you could set a threashold for the number of these 'unresponsive' threads.  When this was hit, CF restarted itself.  In CFMX I do not see this anymore, well, you might see it in the CFMX Standalone version, but not the J2EE version.
>
> Better to find out why you have these long requests.  Is your app DB intensive?  I have apps on intranets that are and have the timeout set to 180secs.  Maybe you have one page running a nasty SQL that needs to be tuned up?
>
> Anyone know of similar settings for JRun????
>
> --
>
> ---
> Douglas Knudsen
> http://www.cubicleman.com
> "If you don't like something, change it. If you can't change it, change your attitude. Don't complain." - Maya Angelou
>
> how does one free that thread?  its killing my webserver, and its
> getting to be a problem.
>
> tw
>
> On Thu, 05 Aug 2004 14:13:23 +0000, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > when the requesttimeout wall is hit, the user gets a message.  Can't trap this one though, sucks.  Note that when this occurs, the thread tied up in this request is not freed neccessarily.
> >
> > --
> >
> > ---
> > Douglas Knudsen
> > http://www.cubicleman.com
> > "If you don't like something, change it. If you can't change it, change your attitude. Don't complain." - Maya Angelou
> >
> >
> >
> >
> > hi there.
> >
> > if you have a request timeout setting of 30 seconds, and that time
> > threshold is hit, what if any notification does the requesting
> > template get? anything? an error that can be caught?  it seems like
> > the page churns and churns, for 30 seconds, and then just nothing.  no
> > error, no nothing, just sits there...then eventually my server
> > crashes...WTF?
> >
> > --
> > tony
> >
> > Tony Weeg
> > human.
> > email: tonyweeg [at] gmail [dot] com
> > blog: http://www.revolutionwebdesign.com/blog/
> >
> > Check out http://www.antiwrap.com to send websites to your friends.
> >
> >
>
>
  _____

---

[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

---