Ticket #344 ( Pending Customer )

Short Description Timeout problem
Entered By: gaucho When: 1999-06-28 18:42:57 Build: 2 beta
Categories Type: Problem   Department: Product   Category: Not Categorized
Thank you again for coming last friday to help us with our application. At this point in time, we have another problem. We are experiencing a problem with the 'timeout' option as well as the 'sweep' option.

After all of the sessions have been filled, the sessions that should be timed-out are not correctly doing so. Although there should be some available connections, I keep getting the error of 'all connections are full' when in reality, there should be a fair amount of connections available. When I try the sweep function, it crashes the application. Also when I try to manually stop a session, it sometimes crashes the system too.

I feel the code in the templates are correct, but I can't seem to figure out why the sessions are not timing out correctly. The timeout is set to three minutes, but a connection that is 10 minutes old, is still considered active and unavailable to a new user.

Any suggestions? Chuck Kang Joe Sabado Student Information Systems, UCS

Append By: WindSurfer  When: 1999-06-28 22:55:38  New Status: Pending Customer
Comment First, please send any drwtsn32.log file from \winnt to surfer@ieinc.com and reference ticket #344.

Using the same code level here the same thing isn't happening, so the crash log is critical to fixing this problem.

We will continue to try to reproduce the problem.

Append By: WindSurfer  When: 1999-06-28 23:09:37  New Status: Pending Customer
Comment When you try to connect to the system, please try to use the refresh button to ensure that the page indicating no sessions available isn't coming from the cache-- in trying to reproduce this error, there were times when I got the message of no sessions available, but was able to overcome it by refreshing the browser.
Append By: gaucho  When: 1999-06-29 16:41:24  New Status: Pending IE
Comment We tried the suggestion above. It doesn't fix the problem. All 50 connections we have defined have all timed out and all of them are marked "Active" If this is of any help, I don't know if this problem is related to the Sweep Function not working. What I think is happening is that the timeout mechanism is NOT resetting the connections and not marking them as either available sessions or making the timed-out session available to new users.
Append By: WindSurfer  When: 1999-06-29 16:59:15  New Status: Pending Customer
Comment What happens when a user selects logoff? You can acquire one of the sessions in the DevCenter and select logoff (with trace on) to see what happens...

Also, can you please send the drwtsn32.log file, or the end of it if it is very large, so that we can determine why the sweep is misbehaving.

A new version that incorporates your changes and is a "formal" build is now available at ftp://ftp.ieinc2.com/pub/surfer/t2_0_4O.zip -- when possible, please test this build for the timeout functions, sweep and so on.