Changing request timeout

[Adrian Lynch]

Running an application on Railo 4.2.1 and testing locally on the Express version (Jetty).

I can't seem to increase or decrease the request timeout from it's current 50 seconds.

It's set to 50 in the server admin.

I change it, restart Railo, restart Jetty but still it times out at 50 seconds.

I started off trying to set the request timeout in a script component, read around that if wasn't suuported, moved to a tag based component, moved to setting it in App.cfc, then went to Railo admin. None seem to have changed the timeout.

Am I missing something?

Any pointers to bugs I might not be finding on the googles?

I won't be able to move this app to a newer Railo or Lucee.

Thanks.

Adrian

[Kolbenschlag, Clemens]

Hi

 

Did you set it only in server admin or in the web-admin too?

I change the value always in web-admin.

 

Cheers

Clemens

--
Did you find this reply useful? Help the Railo community and add it to the Railo Server wiki at https://github.com/getrailo/railo/wiki
---
You received this message because you are subscribed to the Google Groups "Railo" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/railo/CAH368ST%3DPsdhixpGVObC-c9GwG67z-2P%3DgiiYwDaK0A7A_q6dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Adrian Lynch]

I tried both.

It's got to the point where I can't cause a timeout to happen now.

I'm starting with fresh code to see where I'm going wrong.

A

To view this discussion on the web visit https://groups.google.com/d/msgid/railo/2382D393ED37BF408BBEBCFDF3C5FBE30A7852%40Media-Ex01.media-muc.de.

[Denard Springle]

Hey Adrian,

   Couple of thoughts on this..

   First, if you have code that is generally taking more than 50 seconds to execute, unless it is a known long running process (like a scheduled task), then your best bet is to figure out why it takes that long to process and optimize the code (and possibly the database and query if those are involved).

   Second, are you saying that something along the lines of

setting requesttimeout="999";

is not working within the code that is giving you the timeout issue? If so, I don't know of any bugs that might cause that, but you could try dropping down into Java and setting it there:

createObject( "java", "coldfusion.tagext.lang.SettingTag" ).setRequestTimeout(javaCast( "double", 999 ));

Can't remember if 'coldfusion' needs to be changed to 'railo' or not tbh... haven't had to drop into Java for this since ACF9 and don't have the time to go through the Railo source atm ;)

And, lastly, you can do an in-place upgrade of Railo 4.2 to Lucee 4.5 (see: https://bitbucket.org/lucee/lucee/wiki/Migrate_from_Railo) - no reinstall needed, just a few simple steps. Unless you have made some specific modifications to the way Railo operates, I'd suggest going the upgrade path to be on a supported platform. There are already several security issues that have been fixed in Lucee but still affect Railo servers in the wild - this alone should be reason enough to migrate :)

Hope that helps!

-- Denny