Dynamics AX EP - session timeout

(0) Share

Report

Posted on by Community Member

Hello,

I have realized that there is default timeout for AX EP (AX 2009) for 30 seconds.

How can I limit the timeout of the session (or unlimited timeout , if possible - if not what is best practice for unlimited timeout)?

Thanks :)

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Suggested answer

Umesh Pandit 9,315 User Group Leader on at

Like (1)

Report

Hi Eitan,

Configure session and server state settings in the web.config file

Session and server state settings in the Enterprise Portal web.config file directly affect how the server manages user sessions, caches objects, and allocates memory. By adjusting these settings, you might improve Enterprise Portal performance. Review the following descriptions carefully to understand which settings might have the most helpful impact on your Enterprise Portal environment, and then monitor configuration changes in a test environment.

You can customize the following session settings in the Enterprise Portal web.config file.

Timeout: Specifies the time, in seconds, before an inactive user session is ended. The default value is 30. If you increase the time-out, the session remains active longer and does not have to be rebuilt when the user sends another request. If you specify a longer time-out value, the system uses memory to store session state. As you adjust this setting monitor the performance cost of creating new sessions against storing session state in memory.

Please check this link:

technet.microsoft.com/.../jj677308.aspx

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I would like solution for ax 2009.

I have changed in web.config as msdn.microsoft.com/.../system.web.sessionstate.httpsessionstate.timeout(v=vs.110).aspx

same timeout.

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

You have two timeouts here. The request timeout and the session timeout. Normally a session lasts for 20 minutes (default on IIS, as far as I know). A session timeout happens if there are no new requests from the client to the server from that browser. A request timeout is when one single request takes too long to process server side. You don't want these to last "forever", or basically too long. It would open up for a setup where multiple requests would eat up too much of the servers resources, and you don't want that. It makes sense to let both requests and sessions be flushed out in a sensible time fashion, in order to release resources.

If you for any reason have a resource (a page, a report, a service) you know may need a long time to process, you should consider configure this specific resource to have a designated request timeout. Or you should consider redesign for better and more optimal performance.

I wonder why your pages take more that 30 seconds to open. Is this a symptom of bad performance or lack of resources? You should be aware that IIS will often continue to work if there is lack of available memory, BUT it will operate extremely slowly. Maybe the reason why some pages are being returned slowly us due to lack of performance and instead of tweaking the timeouts you should add more resources?

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

I think, the problem was on vertical application (an enhenchment of AX), because that doesn't happen for the 'role center' which is not vertical, so there was an internal timeout of internal object (not matte what web.config is declared).

You can consider this issue as closed one.

Thanks, anyway.

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

Good job, Eitan! :-)

Was this reply helpful? Yes No
Adrian Pascari A 1,683 on at

Like (0)

Report

HI. Can you help me?

I have the same issue. How you fixed it? changed something on AX side?

Was this reply helpful? Yes No