[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference forty2::x500

Title:X.500 Directory Services
Notice:Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL
Moderator:FORTY2::PULLEN
Created:Tue Jan 30 1990
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1016
Total number of notes:4299

848.0. "Unhandled exception in association sender" by AIMTEC::ZANIEWSKI_D (Why would CSC specialists need training?) Tue Jul 09 1996 02:30

T.RTitleUserPersonal
Name
DateLines
848.1FORTY2::PALKATue Jul 09 1996 13:278
848.2AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Tue Jul 09 1996 17:093
848.3AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Wed Jul 10 1996 01:1419
848.4FORTY2::PALKAWed Jul 10 1996 13:4125
848.5AIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Wed Jul 10 1996 18:237
848.6Solution ?EVTAI1::9dhcp137.evt.dec.com::lepaulFri Apr 04 1997 18:0011
X.500 Version 3.0 (No eco).

Hello,

I've a customer with the same error message in .0. 
This customer have been using ALL-IN-1 with X.500 
for 3 days. X.500 is hang two times each day.

Any idea how dave solved this problem ?

Pierre.
848.7FORTY2::PULLENJulian PullenFri Apr 04 1997 19:1310
    Have you checked the DSA's resources. X.500 uses OSAK and OSAK
    does not behave well when it hits a resource limit. Look at the
    quota "Buffered IO byte count", "Buffered IO limit", "AST limit"
    and "Paging file" of a running DSA. If any of these gets low you
    should up the quota. See "X.500 problem solving" chapter 7.

    Julian 
    

848.8Quotas seem decrease more and moreEVTAI1::10dhcp195.evt.dec.com::lepaulThu Apr 10 1997 13:2136
Julian,

I try to tune correctly the DXD$DSA_SERVER process. 

- First i've noticed the AST_LIMIT was too low. I've 
increased it from 100 to 200. 

- Then the process was in RWMBX. With SDA i've noticed 
the IO_BUFFERED, FILE_LIMIT was low too. I have increased
them from 100 to 200.

-Today the process have been running for 22 hours without 
problem. But the free AST_LIMIT is 60, the free IO_BUFFERED is
69. It seems they are decreasing more and more. The dsa 
counters show there is not an heavy load (see at the end).

-There are two applications which are using X.500 (XDSU and
ALL-IN-1).

I'll let you inform if the quota decrease more and more.
If you have any comments or recommendations?

Thanks in advance,
Pierre.

***
Dua bind accepted 	363
Search 			2542
Read 			5317
Compare 		54
List 			4
Result 			9246
Add 			496
Remove 			206
Mod 			775
***  
848.9EVTAI1::10dhcp195.evt.dec.com::lepaulThu Apr 10 1997 15:2619
Julian,

This morning 		09:00 am
	Free AST_LIMIT 		60
	Free IO_BUFFERED	69
	Free FILE_LIMIT		150

Three hours after...... 12:00 am

	Free AST_LIMIT		24
	Free IO_BUFFERED	27
	free FILE_LIMIT		105


I've advised the customer to stop and start the DSA and
during the noon to increase the quotas. But this seems only a 
workaround. Tuning problem or ......?

Pierre.
848.10FORTY2::PULLENJulian PullenThu Apr 10 1997 18:2515
Pierre,

    We have just noticed an error. From V3.0
    onwards the DSA does not default the
    DSA Idle Disconnect Timer correctly.

    You can set it to its default value

    ncl> set DSA Idle Disconnect Timer 300

    If you do this the idle associations
    will timer out after 5 mins and your
    resources will be released.

    Julian
848.11Should all systems set the timer to 300?GOBUCS::COOLEYMegan and Michelle's DaddyThu Apr 10 1997 18:556
    I just noticed the "Idle Disconnect Timer" = 0 on all my Unix systems.
    
    Is this causing a resource problem on Digital UNIX as well?
    
    Regards,
    Warren
848.12FORTY2::PULLENJulian PullenThu Apr 10 1997 19:524
Yes you should check all X.500 V3.0 and later system and
if "Idle Disconnect Timer" = 0 set it to 300

Julian
848.13a-109.tunnel.crl.dec.com::FORTY2::PALKAAndrew Palka Altavista DirectoryFri Apr 11 1997 11:5314
What this means is that clients are not disconnected if they
dont use the association.
This ties up some resources in the DSA which might otherwise
be released.
Normally clients will eventually disconnect, but you might have
some people who leave the client running while they are out of
the office.

I dont know if setting the idle disconnect timer will improve
the infobroker resource problems that some people see. I doubt it,
as I doubt that infobroker even realises that it has been
disconnected until it tries to send another request.

Andrew
848.14EVTAI1::10dhcp195.evt.dec.com::lepaulFri Apr 11 1997 17:189
Re .10

Julian,

With the dsa idle disconnected timer set to 300 (5mns) the
behaviour of the DSA is correct.

Thanks,
Pierre.