I'm already familiar with the -r option of analyse.shm but it is the equivalent to: LIST.READU EVERY. I only need this part:
Active Read Waiters: Owner Waiter Device.... Inode.... Userno Userno 1074003970 41292 671 547 I an extract this part from the output of analyse.shm but this report takes a lot of time producing all of the grouplock and record lock information. Ideally, i'd need a switch to give me only this part + the key or group where the problem is occuring. ----- Original Message ---- From: David Scoggins <dscogg...@gmail.com> To: u2-users@listserver.u2ug.org Sent: Monday, February 23, 2009 9:59:29 AM Subject: Re: [U2] [UV] Deadlock report ? Take a look at analyze.shm (see the 'Administering Universe" manual), IIRC the -r option in particular should give you just the record locks. On Sun, Feb 22, 2009 at 2:00 PM, Jacques G. <jacque...@yahoo.com> wrote: > Hello, > > I was wondering if there is a deadlock report feature in Universe. We have > web services that need to call legacy subroutines and these sometimes make > use of READU clauses without the locked statements. > > Since our pooled webservices have to run between 14 and 92 transactions a > minute these READU statements can cause timeouts for transactions waiting in > line. > > The transactions causing the blockage do not necessarely remain blocked for > very long. It can be anywhere from 30 seconds to half an hour however > between the time the problem occurs and is detected and reported by our > clients. It has usually passed before we can do a LIST.READU EVERY to detect > which file is the one being blocked. > > I am only interested in the list of deadlocks that show "blocked" users at > the end of the LIST.READU command (the list of users running a READU and > waiting to obtain the lock) and not the huge GROUP locks report which > preceeds it and which takes time to produce. There does not appear to be a > switch to LIST.READU to only show the deadlock section. > > I've thought of running periodic LIST.READU EVERY every 2 minutes but with > over 800 users online + the numerous webservices transactions, it just takes > to long (over 4 minutes) to produce the list. > > So I've wondered if there isn't a reporting feature I could turn on so that I > could see the deadlocks that occured during the day. This way, I could > cross-reference the timeout problems with the deadlock list and see which > file being accessed is behind the blockage. > > The info I'd need is: > Time, blocked User, File, Key, Id of blocking user ------- 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/
