going into idle state?

[vksrinu]

I am migrating our apps to apache2.0/Coldfusion9. The migration is still in testing phase. I facing an issues where if we  have not accessed sites for some times then it looks they are going into an idle state. where in once come and access its taking a little time to start off the application and display home page. Either apache/CF does not show any logs. any comments.

[Dave Watts]

You can increase the Application timeout in your Application.cfm/cfc file, or change the default and maximum values in the CF Administrator.

Dave Watts, CTO, Fig Leaf Software

[Dan_Bracuk]

You are describing expected behaviour.  The application timed out so when when you accessed the site, your onApplicationStart code had to run.  Having said that, if nobody is accessing the site, doing something about this might not be the best use of your time.

[vksrinu]

we have application timeout set to 2 days but if the site is not accessed for more than 4-6 hours its going into idle state. i have application.cfm not application.cfc (old code migrating to CF9).

[Owainnorth]

In which case, I'd say first thing to do is change your Application.cfm to .cfc format. You can then just get it to email you in the onApplicationEnd() and you'll know exactly what's going on.

Agreed CF will be the biggest issue here, but remember that when used regularly files are cached everywhere from the disk cache, controller cache, and even RAM on the server. It will always take longer for a page to first load after a period of inactivity.

[BKBK]

vksrinu wrote:

we have application timeout set to 2 days but if the site is not accessed for more than 4-6 hours its going into idle state. i have application.cfm not application.cfc (old code migrating to CF9).

Let's assume you have a tag like this in your application file:

<cfapplication name="my_app" applicationTimeout="#createTimespan(2,0,0,0)#" sessionManagement="true" sessionTimeout="#createTimespan(0,0,20,0)#">

Is everything then nice and fine? No, not if you saved the file as application.cfm. So, make sure the file is named Application.cfm, with capital A.

[vksrinu]

we are Application.cfm only. we have below code.

<cfapplication name="OLPOrders" sessionmanagement="yes">

we are using the default CF administrator settings for application/session timeouts.

[BKBK]

vksrinu wrote:

we are Application.cfm only. we have below code.

<cfapplication name="OLPOrders" sessionmanagement="yes">

we are using the default CF administrator settings for application/session timeouts.

I would suggest you use

<cfapplication name="OLPOrders" applicationTimeout="#createTimespan(2,0,0,0)#" sessionManagement="yes" sessionTimeout="#createTimespan(0,0,20,0)#">

This way, you can be sure you completely overrule the Administrator, at least, as far as the timeouts are concerned. in any case, it is worth testing.

[Adam Cameron.]

Well... troubleshoot it the same way you'd troubleshoot any performance "shortfall".  To start with, switch debugging on, leave it over night, hit the site, and see where the slowdown is coming from.  You might find your DB is closing its connections, or something similar.

--

Adam

[vksrinu]

may be i can try this...i will try opening the CF monitor and will keep it for some time.

Thanks

Srinivas