I don't think that UniObjects puppy runs an UDT.EXE - It runs a RPC server variant instead... a matched pair of "udapi_server.exe" and "udapi_slave.exe" running under the "unirpcd.exe" tree.
I would look at your telnetd service as spawning them with "login: " prompts scrolling by on the client side... (Esp if under the process explorer they are under the telnetd service process) What I see is when the "login: " repeats, UDT starts a new UDT.EXE and the old one dies at that moment. I changed my timeout settings in UniAdmin to slow this process down a bit. The other thought would be phantoms spawning and not killing their UDT.EXE. These puppies appear as thou they do not have a parent process if you login, spawn phantom, logout. The reason would be that the parent PID handle is no longer valid. On windows 2003 they seem to die, but on your 2000 box they could be staying alive... (evil?) How fast are they stacking up? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hammer, Mark Sent: Monday, May 08, 2006 9:27 AM To: [email protected] Subject: RE: [U2] "extra" UDT.EXE's Thanks to Marc/Victor/Anthony for the responses. We do have one VB.NET app that uses UniObjects to access the DB -- that's about the only thing I haven't totally exhausted yet... I'll see if I can find anything odd occurring with those processes. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Victor St Clair Sent: Thursday, May 04, 2006 3:25 PM To: [email protected] Subject: RE: [U2] "extra" UDT.EXE's Hello Mark We had a situation recently that sounds similar to yours, but only on a development machine. Unfortunately it happened over the weekend and the system admin rebooted the box, to get rid of the extra udt.exe processes, before I could get in to examine the situation thoroughly. In our case there were only 4, but they were all grabbing all the cpu they could get, pegging it out at 100% all the time. We're on UniData 7.1 on W2K3. In our case, I believe the cause was terminated UniObjects connections. A UniObjects process was calling a UniBasic program via the uniCommand method. The UniBasic program had a debug statement in it, which caused the UniObjects app to hang. It had to be terminated. Don't know if you're using UniObjects, but maybe our experience will give you a hint you can use. Victor St. Clair -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hammer, Mark Sent: Thursday, May 04, 2006 11:27 AM To: [email protected] Subject: [U2] "extra" UDT.EXE's Has anyone ever had a problem with extra unidentified UDT.EXE processes spawning -- and then never dying? For example, on our main server running Unidata 6.012 on Windows 2000, the UniAdmin tool usually shows around 100 connections during production hours. When I then dump the process list end examine it, I count over 300 UDT.EXE's -- these extraneous processes consuming an average of 2.3MB - 2.5MB of RAM and 0% processor. This is after about 3 days of uptime, indicating that the number steadily grows as time passes -- forcing us to reboot about twice per week. Hardware: Dell 2650 2GB RAM dual 2.GHz Xeons split backplane, RAID 5 on the DB volume Thanks, Mark J. Hammer Systems Analyst Manitowoc Beverage Equipment 812-246-7000 x360 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
