Perhaps farfetched, but could someone have been trying to rebuild an index? This happened to us earlier this week. We got up to over 200 udcs sessions; I couldn't kill them and stopping unirpc didn't help. As soon as we realized what was going on, the user terminated her BUILD.INDEX and everything went back to normal. HTH John Cassidy Unix Sys Admin DCCCD
>>> [EMAIL PROTECTED] 1/18/05 4:17:08 PM >>> Suddenly today we started seeing 'No more LCTs' when we tried to log in. Checking the process list shows LOTS and LOTS of udcs and udapi_slave processes, which I can tell from the userid are coming from my UniObjects for Java code. But I don't hold sessions open. I connect, perhaps run a subroutine, and disconnect. We've made changes to the web server (where the UOJ code runs) lately, most notably changing to JDK 1.5. But I can run the same code on the same web server against a different UniData instance, and I don't see the problem on that unidata. We've got unirpcd shut down for now, and will stopud/startud after hours. Any ideas why the RPC daemon may have suddenly lost its senses? -- Wendy Smoak ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
