How to track down unexpected session timeout in asp.net 4.0

Question

0.00/5 (No votes)

See more:

Hi ,

I am experiencing session timeout issue in between , it happens any time . I checked IIS configuration and all other possible scnerios in web.config file as well. All is working well .

But not sure why there is sudden session timeout in my application.

any suggestion to check ? any code or tool to track this problem if its coming from some code level logic

Posted 2-Jun-15 0:18am

Torakami

Add a Solution

Comments

Kornfeld Eliyahu Peter 2-Jun-15 7:39am

Are you handling the Session_End event in Gloabal.asax? It may give you some info...

Torakami 2-Jun-15 8:15am

yeh i have a debugger on my session_end , but the problem is usuaully occurs on live server and not on development side

Torakami 2-Jun-15 8:18am

can you provide me some set of stements that will help me to get the information in session_end event while debugging

ZurdoDev 2-Jun-15 14:39pm

Check event log. Also, how do you know the session is ending. What are the symptoms?

Torakami 3-Jun-15 1:33am

I have other page , sessiontimeout.html , it throws on that page ,

ZurdoDev 3-Jun-15 7:19am

I don't know what that means. "It throws on that page." What does that mean?

Torakami 3-Jun-15 8:30am

when it ends the session automatically , i am navigate the user to sessiontimeout page , but session end is happening quite often and i am aware that this is session time out coz I am navigating to sessiontimeout page

ZurdoDev 3-Jun-15 8:39am

It is possible there is a logic error with the code you are using to redirect to sessiontimeout page.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)