Phil - Wednesday, May 12, 2010 11:52 AM:
My question is this: Is Aras supposed to load VERY slowly when bringing it up for the first time? From the time you enter the URL to the time the login dialog box is coming up can be over 30 seconds.
After the user has gone through the login process once, it goes much quicker after that, but the initial login is a bear. I've noticed that the same phenomena happens when a user doesn't access the system for a while.
I know I can't precompile the software, and I've already changed the application pool settings so that the pool doesnt recycle every 30 mins. Are there any other settings/configuration changes that could be recommended to remedy this?
hiro - Friday, May 14, 2010 5:39 AM:
I experienced the similar issues and I'm also gathering more info now.
In my case, I found out there are several kinds of causes below and each would result in different timing for response delay to occur.
As for server side problem: After nobody access for a while , e.g., 20 min, only the first access user has response delay ...
- In proxy env, because of invalid proxy setting, Proxy server blocks CRL validation request for .NET assembly 's authenticode signature to CA site on the Internet. Thit makes initial loading of .NET Assembly waited about 2~3minites (= connection timeout 30sec x retry count 4~5). You can watch the situation by packet capture on IIS server machine.
- To prevent IIS application pool from restarting, please check its setting, e.g. the recycle condition or IdleTimeout(default 20min) . especially, the latter is often passed over.
As for client side or network setting problem: each of users may have some delayed issues...
- Invalid IE proxy setting, that could causes wrong HTTP request loop.
- Anti-virus software takes long time to scan downloaded files.
I would be happy to help you.
hiro
