| I've made quite a few bug fixes to the VTX communication layer (DASL) where
network resources were not being properly deallocated. I've only got one
situation where the error mesage DSL-W-DUPOBJ is being returned now. That's in
the case where you do a START COMMUNICATION, a client logs in, then a STOP
COMMUNICATION (where a VTX client is still connected), then another START
COMMUNICATION. In this case, you need to stop the outstanding sessions before
you can re-start communciations.
I've also fixed the bug whereby if STOP COMMUNICATIONS failed, then control was
never passed back to VTXCTL and the server had to re-started.
I've also fixed up DASL and the server so that if too many clients try to
connect and the server process's BYTLM is exhausted, that each client will just
get a "server not responding" message (instead of hanging). Now, the service
provider will be able to do a STOP COMMUNICATION and a START COMMUNICATIONS
to get communciations going again (that's also improves on the current situation
where the server would have had to be re-started.)
Also, if the service provider tries to start communication where the server
doesn't have enough BYTLM, the status "DSL-W-EXBYTLM" is not sent back to VTXCTL
with the message "Server process has exceeded its BYTLM quota: increase quota
and restart server"
If anyone wants to get this version of DASL/VTX server, I'd be happy to suppply
same.
Ronan
|