User-Defined Jobs | How to increase Session timeout for a longer script

[Sids]

Hi Group

We have a User-Defined job which invokes an ASP script through Open
URL functionality.
When I invoke simple and small scripts this job works just fine and
returns me expected results as it returns when the same ASP script is
invoked through URL using a web browser.

e.g. http://10.40.7.161/cms/plugins/testJob.asp

This ASP script is kept under Plugins folder and can not be executed
as plugin or through content for obvious reason that we are trying to
schedule it.

The mentioned scipts once invoked through the user-defined job, logs
in the CMS through RQL using a specific user assigned for usage of
this script only and then it performs some more SQL and RQL actions
and finally it logs off the logged in user.

Issue happens when this ASP script is a little more longer, the user-
defined job returns Operation Timed Out whereas the exactly same
script runs fine when hit through web browser.
We have already defined Server.ScripTimeout as 720000000 which is
longest I can as per my understanding.

But the user defined job always return Operation Time Out and ignores
the timeout setting.
It is not about what the script do but whatever it do, if it takes
long to do then user-defined job throws error Operation Timed Out in
Log.

How can I force the User-Defined job to execute this script for longer
duration or in other words increase ScriptTimeout for this job?

I had raised the same question to Open Text but as usual their
tendency is to skip answering and forcing customer to go to
Consulting Services and more ridiculously they are offering us to get
consulting services to debug the ASP script we have, even after
clearly mentioning that ASP script runs fine in web browser and shows
no code issues in no case. open Text says we dont provide support
around user-defined jobs as those are custom created like we are
asking them what to write in our ASP script.

Has anyone faced this kind of problem before and has any clue how to
get through it?
Any pointers will be highly appreciated.

Thanks,
Sids

[kimdezen]

I'm no expert with IIS, but perhaps you can look at chaning the
default time out setting within IIS:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/2275a2ba-5b12-4e18-8266-8a3b0678e419.mspx?mfr=true

See if that helps!

On Dec 18, 11:30 pm, Sids <progsudhan...@gmail.com> wrote:
> Hi Group
>
> We have a User-Defined job which invokes an ASP script through Open
> URL functionality.
> When I invoke simple and small scripts this job works just fine and
> returns me expected results as it returns when the same ASP script is
> invoked through URL using a web browser.
>

> e.g.http://10.40.7.161/cms/plugins/testJob.asp

[Richard Hauer (5 Limes)]

Hi Sids,

There are actually 2 timeouts you are fighting here. The first one,
as Kim mentioned, is the amount of time IIS allows for an ASP page to
complete. That timeout value is set with IIS. My guess is that if
your script runs OK in the browser then you aren't hitting that
timeout.

The other one is the amount of time RedDot allows for a user defined
job to return a value. That has nothing to do with ASP per se, but
the job being executed needs to return something in a timely fashion..

There are some values in the RDServer.ini that contribute to this
second timeout. They are as follows, shown with their default
settings.

;begin timeout settings
[URL]
receivetimeout=10000
resolvetimeout=1000
sendtimeout=2000
connecttimeout=1000
;end timeout settings

I'm pretty sure these are only used when executing a URL type job
though - but I suspect that's what you are doing.

Short of fiddling those settings you could execute your task
asynchronously. I.e. have the job call a URL that is a page that
calls your URL but doesn't wait for a response, simply returning "OK"
so the User-Defined Job returns straight away and your task continues
to run in the background (which is how we do it normally).

HTH.

Regards,
Richard Hauer
====================
5 Limes Pty Limited
www.5Limes.com.au

On Dec 22, 11:03 am, kimdezen <dasw...@gmail.com> wrote:
> I'm no expert with IIS, but perhaps you can look at chaning the
> default time out setting within IIS:
>

> http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Librar...

> > Sids- Hide quoted text -
>
> - Show quoted text -

[Sids]

Hi

Thanks for your valuable pointers guys.

@Kim: I did try increasing the IIS timeout from default value of 90
seconds to 180 seconds and it did not seem to help, though I was
thinking about trying a very high value like 720 seconds and if that
works then bringing down the timeout to a logical and optimized
limit. But the complication is we have common CMS server for both Dev
and Prod so increasing timeout to such a high limit needs to be
justified before I get a permission to do that. And I will try to.

@Richard: The settings you have mentioned fits to be causing the
script to abruptly timeout even after I doubled the initial value set
to default 90 seconds on IIS, though as I have mentioned above I will
try to increase the timeout a little more to be sure that this is not
the one setting which can help. I will take a look into these settings
and will try to see if that helps.

Thanks,
Sids

[Sids]

Hi

Increasing timeout did not help at all.
And settings which Richard has mentioned are not there in the
RDServer.ini file we have.

Now question is whether "not having" a timeout in RDServer.ini can be
causing an issue?
Does CMS (as in our case these timeouts are not even there in
RDServer.ini) still has a value defined for the mentioned timeouts or
not?
Any further pointers will be highly appreciated.

Thanks,
Sud