Re: I-STAR spawns child problem

LUZURIAGAM@law.stmarytx.edu wrote: > I've been experiencing problems whereby in certain > instances I-STAR creates another child process. > When this happens no one is able to connect to the > SERVER via I-STAR until the child process is > killed. I-STAR seems to be working fine until I > enter a wrong name or password when connecting. > This spawns a new sqlexecd process and prevents > any further access to the database via I-Star > until I kill the second process. We started noticing a similar symptom in 5.03 UC1. In our case our dbservername for the online instance did not exactly match with the computer name. Setting the server name in an sqlhosts file usually helped but in some cases we still experienced hangs. Upon closer inspection we would find a single process on the client with two TCP ports open to TWO sqlturbos on the server. It always hangs in such cases. This symptom did not occur on any release up through 5.02 UC1. When we set the dbservername to match the computer name and also set sqlhosts to reflect that our problem went away. > We're using I-NET 5.01 for Windows and Online > Verion 5.02UC6, with the latest vesrion of I-STAR. ^^^^^^^ I don't know if the same symptoms occurred for us on this version as we were up on it for only a few short painful hours. Beware of this release, it has far more serious problems than ISTAR hangs. Ken Miles Hewlett-Packard kenm@vcd.hp.com