D
dbeavon
Guest
There is another thing that is bothering me about the behavior of the client-server sessions that are "stuck". As far as I'm concerned, the 4GL sessions in PASOE should always break themselves free after 40 seconds ( based on client session parameter -lkwtmo 40 ). The only resource contention that I see is on a single table. And if records in that table are not made available to the remote client session, then the remote session should raise the STOP condition after 40 seconds. I shouldn't have to introduce any explicit code to make that sort of thing happen (eg. by using STOP-AFTER) No matter how I look at it, I'm still suspicious that there is some unreasonable blocking that is taking place between the _mprosrv process and the remote 4GL session.
Continue reading...
Continue reading...