Yeah, that's what I've been doing, I've taken telnet and SB out of the picture. This is specifically through udt.exe on the server, which logs me into unidata demo account.
There is no ON.EXIT in VOC. Process Explorer didn't tell me anything, just highlighted it red as it was trying to terminate. Nothing that we know of has changed on the server. We checked windows updates in add/remove, nothing recent. We have not updated the database or increased licenses since we've been live on this server. No changes to unidata configuration. No new hardware. No errors re": existing hardware. Server had been rebooted about a week earlier, so even if we had some updates we didn't know about (auto update is turned off), they would have been put into effect after that reboot. I'll recreate situation and check PORT.STATUS. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Colin Alfke Sent: Thursday, June 24, 2010 10:14 AM To: 'U2 Users List' Subject: Re: [U2] UniData 'QUIT' If you were on *nix I would suggest looking at your wtmp file. What's changed on the server? Did you add more licenses without updating udtconfig (or made changes to udtconfig)? Is there an ON.EXIT VOC item (not likely in the DEMO account as well)? Even though you don't see them through listuser I wonder if PORT.STATUS PID XXXX CALL.STACK could tell you anything. Look at the processes using Process Explorer or Process Monitor from <http://technet.microsoft.com/en-ca/sysinternals/default.aspx> which may provide clues as to what it's hanging up on. What happens if you connect directly to udt.exe on the server (rather than going through telnet)? Hth Colin Alfke Calgary, Canada -----Original Message----- From: Amy Cook As a test, a co-worker suggested I see if the time increased with multiple sessions. Again, udt'd into demo account, issued quit command: 1 session = 3 seconds 2 sessions = 5-6 seconds 4 sessions = 14 seconds 8 sessions = 1st ended at 21 seconds, 2nd at 35, 3rd at 40, then last couple cleaned up by 50 seconds. I don't necessarily think it matters that they were all logged in as me, but they were, in case that sparks anything for anyone. I DO think it matters that they were all trying to logout at the same time. I currently have 16 record locks, none of them are mine. -----Original Message----- From: Bill Haskett Kevin: Quit may be in UV but it's the "off" command in UniData. I've had to remove it from our application and replaced it with "off", which cleans up our application, then quits. I suspect SB+ doing something similar with "quit" by replacing the default verb with their version. Bill ------------------------------------------------------------------------ Kevin King said the following on 6/24/2010 8:56 AM: > John has an interesting point. I thought QUIT was UV but looking into the > system in front of me right now it appears to be an SB+ thing running SH.OFF > out of DMSH. So that makes me wonder if the file size of DMSECURITY or > DMCONT or one of those DM files might be having an impact? _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
