From: "Glenn Meadows" 

We have/had a similar issue with our Lawson application.  It's a Cobol
program, and the version for Windows 2000 has no ability to know if the
remote session is still connected (dumb program, but that's another
thread). Since we've recently been doing remote access to that machine now
(via VPN), any network burble would drop the connection, and the remote
user would have to login again.  Lawson had no way of knowing that it was
the same user logging in again, or to connect again to the same session, so
it happily creates a new session, leaving the old one orphaned. 
Eventually, we'd hit the maximum number of registered users, and nobody
could log in.  I'd have to stop the Lawson Environment, and restart it to
clear out the orphaned sessions.  Got to be a real PITA as our router was
slowly dying.

Sounds similar.  Many apps don't take into account remote sessions, and
that there might be a break in the connection.

--
Glenn M.


"Geo"  wrote in message
news:41f9a9c7$1{at}w3.nls.net...
> "Ellen K." 
wrote in message
> news:t5civ0tshe0fo0969i7gta1lvq9ub35ram{at}4ax.com...
>
> > My theory is that recent modifications to the application cause it to
> > freeze on the desktop and that is why we are suddenly seeing so many
> > users giving it the three-finger salute.
>
> Have you confirmed that this is the cause? I've also seen this sort of
thing
> happen when there is a momentary network outage, the connection gets lost
> and the far end never gets a reset command. I would think if they kill the
> app that the network driver would at least send a close signal to the
remote
> server.
>
> I'd test it to see if killing the app is causing the resource exhaustion
at
> the db end. Try to make it happen, if it doesn't then it could be some
sort
> of network issue (you had some of those in the past).
>
> Geo.
>
>

--- BBBS/NT v4.01 Flag-5