Re: ODBC not dropping connection following client crash

2004-04-22 Thread Jonathan D Smith




Hi Peter,

Please see my previous message first of all about the helper message error.
Also the fact UniData hasn't cleared the processes up correctly yet, is
because as far as UniData is concerned they probally haven't died, this is
most probally down to your network settings which are not sending the
correct drop signals for UniData to recognise. You will have to wait for
the processes to timeout, UniData (and UniVerse) have a unirpcservices file
which controls the length of time your udservd process will be kept alive.
Also you will not be able to restart the Unirpc process until ALL the
process associated with it, have disappeared as the port will still be in
use. Some O/S's still take some time to free the port after all the
processes have been killed.

You may well need IBM support on this issue, have you tried contacting your
UniData supplier (who should have a support arrangement with IBM) as this
seems as if it could be quite a sticky one to clean up. However it could
all be related to your previous helper error .

Regards,

Jonathan Smith
IBM Certified Solutions Expert
Advanced Support Engineer  - U2 Advanced Technical Support
IBM Data Management Solutions
Support Phone 0800 773 771
Support Mailto:[EMAIL PROTECTED]
http://www.ibm.com/software/data/u2/support -  Open, Query, Update, Search
- Online!


DISCLAIMER:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.

If you have received this email in error, please delete it and notify the
sender immediately.


-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users


ODBC not dropping connection following client crash

2004-04-21 Thread Welsh, Peter
I suspect my Executing helper program problem may be related to a rather
dodgy NT box (NTECCI) that keeps rebooting unexpectedly. The NT box usually
has a few UniData ODBC connections open and it appears UniData isn't
clearing up properly after the client crashes. The result is an awful lot of
connections.

Right now, we are unable to restart UniRPC and the terminal based users of
the system are beginning to get refused connections due to number of users
exceeding licences. Restarting the UNIX box is a last resort for us. Does
anyone have any ideas?

Once again, thanks.

We are running UniData Release 5.1  Build: (2097) on DG/UX Release R4.20MU07

and get the following netstat:
bash-2.05$ netstat -a |grep uv
tcp0  0  dgserver1-uvrpc   ntecci-4462   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2463   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1383   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1690   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4471   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2971   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1375   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4999   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4499   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1387   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2457   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1051   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2728   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1277   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-3677   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1318   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-3418   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2821   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1697   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1797   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1272   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4466   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1701   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1684   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2450   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1330   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2827   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2431   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2948   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4648   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2448   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4996   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1410   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1713   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4641   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4645   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4629   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-3129   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2722   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1335   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4656   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-2337   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1220   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1320   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1325   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-4478   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1088   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1288   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1394   ESTABLISHED
tcp0  0  dgserver1-uvrpc   ntecci-1268   ESTABLISHED
bash-2.05$


Peter Welsh
Senior IT Development Officer
NHS Argyll  Clyde



--
 Welsh, Peter.vcf 
-- 
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users