Home Server
New Blog Posts: Merging Reports - Part 1 and Part 2

rsWebTier Max Sessions not working correctly

edited December 2003 in Server
I'm using the rsWebTier MaxSessionCount to limit connections to the web tier
of my application. Currently, I have that property set to one. I open 1
browser connection: good, second connection gives 'server busy' message when
the user logs in. This seems right.

But after both browsers are closed, I would expect the session count to go
back to zero. It apparently does not because when I open a browser and try
to connect, it still gives the server is busy message and will continue to
until the web tier is unloaded and reloaded again.

Where is this problem coming from, and can I fix it?

Thanks.

Comments

  • edited December 2003
    Additionally, this problem is obviously not a problem coming from the
    RBServer implementation, because I can restart the RBServer but the web tier
    still sends clients to the 'server is busy' page until I restart the web
    tier.


  • edited December 2003

    A web session ends when it times out due to inactivity. (The clients are
    connectionless, when you close the web browser the web tier has no knowledge
    that this has occurred).

    Use the TrsWebTier.SessionOptions.SessionTimeOut property to to specify the
    number of seconds that a session can remain inactive until it expires.


    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited December 2003
    I was already aware of the TrsWebTier.SessionOptions.SessionTimeOut setting.
    I currently have it set to 20, which I would assume means that once a
    session has been inactive for 20 seconds, it is tossed. This is not
    working. My MaxSessionCount is set to 1. Once 1 browser has hit the site
    and then been closed, it is not possible to log onto the site until the web
    tier is unload and reloaded again. It has currently been 3 hours since the
    session was created and it still apparently has not beed destroyed.

    Is there something else that could be causing this to not work? Why won't
    my sessions die?

  • edited December 2003

    The TrsWebTier.GarbageCollection MinSleep and SeparateThread properties are
    used to control how often the webtier garbage collector runs and whether it
    executes in a separate thread.

    Using RB 7.03 and the RB Server demos I performed a simple test.

    1. Ran the RBServer\Demos\Servers\Main app with the default settings. (This
    app is configured to allow an unlimited number of sessions. ) I ran this
    application within the context of RB Services.

    2. Opened the RBServer\Demos\WebTier\ISAPI application and configured the
    WebTier as follows:

    GarbageCollection MinSleep = 3
    SessionOptions MaxSessionCount = 1
    SessionOptions.SessionTimeOut = 5

    3. Compiled and installed to rbWebPub under IIS

    4. Now when I use the web browse to access the report I am able to exceed
    the max session count of 1 by pressing refresh in my browser. Then I receive
    the max session page. Wait for 5 seconds, press refresh again and I can
    access the server again.




    --
    Nard Moseley
    Digital Metaphors
    http://www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.