Vb.net web application Timeout issue

**kenobewan** · Jul 25 '08, 02:48 PM

You may want to use a timer, however threading may also be of use. When your application timesout what do you want to happen?

**dragonjim** · Jul 25 '08, 03:30 PM

Originally posted by kenobewan

You may want to use a timer, however threading may also be of use. When your application timesout what do you want to happen?

I'd prefer to have the user redirected to the login page (login.aspx), but I don't understand why timeout doesn't have any effect.
I'm very new, and don't know what threading means.
Thanks for the reply

**TRScheel** · Jul 25 '08, 03:47 PM

Originally posted by dragonjim

I'd prefer to have the user redirected to the login page (login.aspx), but I don't understand why timeout doesn't have any effect.
I'm very new, and don't know what threading means.
Thanks for the reply

Are you running the project in release? Or debug? I see that you set the setting but if you launch it in VS as debug it will override it.

**dragonjim** · Jul 25 '08, 03:50 PM

Originally posted by TRScheel

Are you running the project in release? Or debug? I see that you set the setting but if you launch it in VS as debug it will override it.

I compiled it and uploaded to the web, with the debug mode turned off. However I don't know if there are other settings that determine debug or release. What is VS ?

**TRScheel** · Jul 25 '08, 04:10 PM

Originally posted by dragonjim

I compiled it and uploaded to the web, with the debug mode turned off. However I don't know if there are other settings that determine debug or release. What is VS ?

Sorry, Visual Studio. I am used to just referring to is as VS.

Could you post a sample web.config omitting secure lines with a sample login.aspx and inside page that requires logging in to see based off your code?

Again, emphasizing omitting secure lines. I dont need to see any sql connection strings, etc.

**dragonjim** · Jul 25 '08, 05:52 PM

Code:

<?xml version="1.0"?>
<configuration>

  <!--<appSettings>
	<add key="connectionString" value="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Projects\.......
  
  <appSettings>
    '''connection string goes here.......    
  </appSettings>

 
 

  <system.web>
   <!-- 
            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.

            Visual Basic options:
            Set strict="true" to disallow all data type conversions 
            where data loss can occur. 
            Set explicit="true" to force declaration of all variables.
        -->
    <!--<sessionState timeout="1" mode="InProc" />--> 
 <!--<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="" cookieless="false" timeout="120"/>-->
    <!--<compilation debug="true" strict="false" explicit="true">-->
    <compilation debug="false" strict="false" explicit="true">     
    <assemblies>
        <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
      </assemblies>
    </compilation>
    <pages>
      <namespaces>
        <clear/>
        <add namespace="System"/>
        <add namespace="System.Collections"/>
        <add namespace="System.Collections.Specialized"/>
        <add namespace="System.Configuration"/>
        <add namespace="System.Text"/>
        <add namespace="System.Text.RegularExpressions"/>
        <add namespace="System.Web"/>
        <add namespace="System.Web.Caching"/>
        <add namespace="System.Web.SessionState"/>
        <add namespace="System.Web.Security"/>
        <add namespace="System.Web.Profile"/>
        <add namespace="System.Web.UI"/>
        <add namespace="System.Web.UI.WebControls"/>
        <add namespace="System.Web.UI.WebControls.WebParts"/>
        <add namespace="System.Web.UI.HtmlControls"/>
      </namespaces>
    </pages>
    <!--
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
        -->
    <!--<authentication mode="Forms">
      <forms timeout="2"/>
    </authentication>-->
    <authentication mode="Forms">
      <forms loginUrl="Login.aspx" timeout="2"/>
    </authentication>
    <!--<authentication mode="Windows"/>-->
    
    <!--
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        
        -->
        <customErrors mode="Off"/>
  </system.web>
</configuration>

Code:

default.aspx
Page Load
 Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
        Dim cmd As SqlClient.SqlCommand = New SqlClient.SqlCommand
        Dim oUser As pharm_users = New pharm_users(Page)
        Dim oPatient As pharm_Patients = New pharm_Patients(Page)
        Dim oConn As SqlClient.SqlConnection = Nothing
        'Session.Timeout = 2
        btnCancel.Attributes.Add("onClick", "return confirm('Press OK to abandon the data, or cancel to continue');")
        btnSave.Attributes.Add("onClick", "return confirm('Press OK to Save and move to the next record');")
        btnNoContact.Attributes.Add("onClick", "return confirm('Are you sure');")

        theChoiceNew = CInt(Session.Item("the_Choice"))
        theCaller = CInt(Session.Item("Pharm_user_id"))
        If Not Page.IsPostBack Then
            If Not oUser.IsLogin() Then
                'Server.Transfer("./login.aspx")
                                Response.Redirect("https://www.sccpkh.com/login.aspx")
                            Else

etc....

**Curtis Rutland** · Jul 25 '08, 06:05 PM

Code tags are a requirement.

Please read the Posting Guidelines

MODERATOR

**TRScheel** · Jul 25 '08, 07:48 PM

Looking at your code I cant find any reason why it wont work. I would suggest tearing it down and trying small samples like the below. Its in C# but the small segments of code should be fairly understandable from a VB .NET view. If you load the page the first time it will say "This should say Hello World" and if you refresh immediately it will say "Hello World". After a minute the session will timeout and reset the process. If your production server has the same result I would suspect there is more to your code than what you are showing, perhaps something holding the session or refreshing it.

web.config

Code:

<sessionState cookieless="true" timeout="1" mode="InProc" />

default.aspx

Code:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="CollegeMain._Default" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
    <title>Untitled Page</title>
</head>
<body>
    <form id="form1" runat="server">
    <div>
        
    
        <asp:Label ID="lblMain" runat="server" Text="This should say Hello world!"></asp:Label>
    
    </div>
    </form>
</body>
</html>

default.aspx.cs

Code:

protected void Page_Load(object sender, EventArgs e)
{
    if (Session != null)
    {
        if (Session["Test"] != null)
        {
            lblMain.Text = (string)Session["Test"];
        }
        else
        {
            Session.Add("Test", "Hello world!");
        }
    }
    else
    {
        Session.Add("Test", "Hello world!");
    }

    //Session.Timeout = 1;
    /* uncomment the above and comment out the web.config line. Should have the same result */
}

Vb.net web application Timeout issue

Vb.net web application Timeout issue

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment