Manuel,
Sorry I wasn't more clear.
We have taf that automatically runs every 15 minutes via crontab. Here's
some crontab stuff:
---- Courtesy of Dale Thomas... hope you don't mind Dale ---
CRONTAB
> > Details of this can be found on page 312+ of
> >the Tango User's Guide (at least in the books for
> >T-3).
> > Basically, you go to your server.ini file and
> >on the CRONTABFILE line, enter the path to your
> >crontab.txt file. Your crontab.txt file will
> >contain the line:
> >
> >10,30,50 * * * * http://xxx.x.x.x/mydir/cron.taf
> >
> >Spaces in this line are critical for proper
> >execution, so pay close attention to the docs.
> >What this does is calls and runs cron.taf at 10,
> >30, and 50 minutes after every hour of every day.
> >(I guess I lied when I said every 10 minutes...)
> >Now that I think of it, since the connections
> >expire after 30 minutes, 20 minute intervals gave
> >us what we needed. [[I also have a VB program
> >that runs in the background, and every 10 minutes
> >it goes through the alphabet doing a 'dir' on any
> >drive connected through the network and writing
> >to a file the time stamp when it was there.
> >Keeps everything from going to sleep.]]
> >
> >Our cron.taf simply goes to each DSN we have set
> >up and does a SELECT on one of the tables, but
> >does nothing with the results. This action is
> >sufficient to keep the connection to the
> >databases alive. And as I said, every time ours
> >hung, it did so while trying to establish a
> >connection to the DB.
> >
In our case we use a Direct DBMS, one for each datasource (the Oterro
connection between Tango and RBASE), ie, each database gets a hit using:
SEL colname from tablename where limit = 1
****************************************************************************
****
Which raises the question... what is the fastest way to hit the database.
Ie, if you have many databases, what is the most efficient set of DBMS's to
use? Does it matter?
The SEL command seems to do the trick without any stress.
Brent
-----Original Message-----
From: Manuel de Aguiar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Saturday, June 30, 2001 12:07 AM
Subject: Re: Tango Service Hanging
>Hi Bent,
>I feel so bad that I cannot contribute to this thread. What do you mean by
>"touches each datasource"?
>TIA,
>Manuel
>
>Brent Skean wrote:
>
>> Troy,
>>
>> Dale Thomas recently had a suggestion about this issue...
>>
>> He uses crontab to activate a taf that touches each datasource every x
>> number of minutes.
>>
>> We use crontab to have our server send @serverstatus data in an email
every
>> 15 minutes. We have now added the touching of the datasources.
>>
>> Brent
>>
>> -----Original Message-----
>> From: Troy Sosamon <[EMAIL PROTECTED]>
>> To: Rbase List <[EMAIL PROTECTED]>
>> Date: Friday, June 29, 2001 1:41 PM
>> Subject: Tango Service Hanging
>>
>> >I thought I would post back to the list in the event anyone else has
this
>> >problem.
>> >I am running Tango 2000, Win 2000, IIS 5, Oterro 2000rt03.
>> >I have found the source of my problem with the Tango server hanging for
a
>> >few minutes on regular cycles. For some reason when the datasourcelife
>> >expires on my Oterro data sources and Tango drops the connection, it
causes
>> >the Tango service to hang between 3 and 8 minutes. Everything works
fine,
>> >users are not dropped, just all Tango services stop for that time
period,
>> >and the Tango users get very annoyed. All other services on the server
run
>> >fine during this time.
>> >
>> >I have found a workaround for the problem by changing my datasourcelife
to
>> >1440 minutes, and I am going to stop and restart the tango service every
>> >night.
>> >
>> >Tech Support at RBTI beleives that it is a setting or several on my
system,
>> >and that this is not a common problem.
>> >
>> >Thanks everyone for your input,
>> >
>> >Troy Sosamon
>> >Denver, Co.
>> >
>
