ADSM-L

Re: Hung Admin Sessions

2001-02-26 11:59:44
Subject: Re: Hung Admin Sessions
From: David_Bohm AT TIVOLI DOT COM
Date: Mon, 26 Feb 2001 09:00:07 -0800
Each of these threads will have at least one other thread associated with
it.
You should find an admin command thread that has a ptid= the thread number
of the session thread.  What this session thread is waiting for is more
output
from that command thread.  You should probably open a problem record on
this.  There have been some situations in the past where there was some
lock contention with certain queries.  It might be possible to figure this
out
from just some additional query and show commands or it might require
a kill -11 so a core dump can be generated and those threads can be
examined.  The point to start with is what those command threads are
waiting for and continue diagnosis from there.

David Bohm
TSM server development
email - dbohm AT tivoli DOT com


>Gentle Greetings,
>
>Has anyone noticed any situations where Admin sessions on the server get
>hung and become "ghost" sessions that will not go away?  Cancelling has no
>effect.  Opening a separate Admin session and cancelling from there has no
>effect.  In some cases, subsequent sessions get hung and a reboot is
>necessary.  And in other cases, there seems to be no adverse side effects.
>
>In this case, I was doing some SQL queries on the database, and two user
>Admin sessions hung and two Query Admin sessions hung.  (Fortunately,
>everything else is continuing to run smoothly.)  Below is the output from
>"show threads" related to these 4 sessions.
>
>We are running 4.1.2 Server on an IBM M80 running AIX 4.3.3.
>
>Thank you in advance for any help and/or suggestions.
>
>Jennifer
>
>----------------------------
>Thread 68: SessionThread
>tid=4437, ktid=34577, ptid=52, det=1, zomb=0, join=0, result=0, sess=31636
>  Awaiting cond 5c355b04 (mutex 301a65b0) at 10009b38 (outGetNext)
>
>Thread 101: SessionThread
>  tid=653d, ktid=69811, ptid=52, det=1, zomb=0, join=0, result=0,
sess=31768
>   Awaiting cond 5c33a484 (mutex 301a65b0) at 10009b38 (outGetNext)
>
>Thread 105: SessionThread
>  tid=6963, ktid=72547, ptid=52, det=1, zomb=0, join=0, result=0,
sess=30446
>   Awaiting cond 5c286354 (mutex 301a65b0) at 10009b38 (outGetNext)
>
>Thread 108: SessionThread
>  tid=6acf, ktid=52079, ptid=52, det=1, zomb=0, join=0, result=0,
sess=31704
>   Awaiting cond 5c1c69d4 (mutex 301a65b0) at 10009b38 (outGetNext)
<Prev in Thread] Current Thread [Next in Thread>