Can anyone tell me exactly what the QUIT verb does? Does it issue a stopudt? Does it also do a 'kill' or windows equivalent of o/s process id? I'm asking because we have a situation where:
1) When I issue the quit command (using demo account for testing purposes), it takes a minimum of 3 seconds now to logout. It's never been anything but immediate up until a week and a half ago. 2) if we have numerous phantoms running, they seems to be hitting this same delay in logging out, and within a couple minutes, that 3 seconds grows to 20 seconds...up to 20 minutes or more...waiting on the other sessions to logout. 3) At the point where it's taking a long time to logout...the database has already released the session. Listuser no longer shows that phantom session. But the Task Manager shows it's still active to the O/S. At first we were focused on the phantoms, but these are the only sessions that really log in, do something, then immediately log out...creating the perfect environment for building up the 'queue' for logout. Since we've been through a ton of troubleshooting already, I'm trying to start over at ground zero and figure out why a simple unidata session to the demo account doesn't immediately log out when I issue the quit command. Any ideas?? TIA, Amy _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
