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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

3700.0. "X Event Queue Monitor..?" by STAR::BOIKO (Heaven..No,it's Iowa/Field Of Dreams) Tue Nov 20 1990 15:52

	Are there any products (DW-Mail,DECwrite, etc..) or internal hacks, 
 which have been instrumented to allow the continuous monitoring of the number 
 of pending X events on the event queue?

	This would be very helpful in analyzing problems associated with the 
 backup of X events because of network delay or link failure.

	Any info would be very helpful...

							Thanks
							-mike-
T.RTitleUserPersonal
Name		DateLines
3700.1some info...WIDGIT::WESTSCARY : A programmer with a screwdriver.Tue Nov 20 1990 18:3738
RE:    <<< Note 3700.0 by STAR::BOIKO "Heaven..No,it's Iowa/Field Of Dreams" >>>
                            -< X Event Queue Monitor..? >-

>>	Are there any products (DW-Mail,DECwrite, etc..) or internal hacks, 
>> which have been instrumented to allow the continuous monitoring of the number 
>> of pending X events on the event queue?

  I'm not aware of any that does _exactly_ what you want..maybe XLiddy ??

  Each application has its own event queue tied to the server (via the
transport layer).  This event queue is of a static size...64k I think.

  When the server gens an event for a particular client it will attempt to
write the event to that clients event queue.  If the server fails to write
the event it will retry a certain number of times before it gives up.  If
the server gives up it deems that client to be a _bad_ client and aborts its
display connection.

  Usually the number one reason why the server can't write the event is due to
the fact that the clients event queue is full...which usually means the client
has either stopped processing events or is unable to process the events fast
enough.

  I do understand that there are other reasons as well...some due to timing
issues...I do not know enough about these to give you any insight...maybe
someone else can :^)

  As I mentioned at the top, XLiddy may help in that it is a 'wiretap'
program...it sees all the requests and events and journals them...with time
stamps.

  This may help you...I'm not sure.

  Gosh...didn't mean to write a book here...  :^)


					-=> Jim <=-