Conference orarep::nomahs::dectrace_v20

457.0. "No end time for "hung" transactions?" by M5::LWILCOX (How about Fireworks?) Mon Apr 07 1997 08:14

Customer on 2.2 on VAX states that they get into a situation where they
have transactions that "hang" for maybe 15 minutes to an hour or so, but
there is no end entry of any kind for these transactions in Trace.  They 
are using ACMS and the ALL class.  He usually doesn't find out that they
got into this situation until after the fact when he's looking at the data
and says "hey, this is good, our longest running transaction was 30 seconds"
and someone else says "no, we hung up for 45 minutes".  In otherwords, he
hasn't looked at anything via RMU/SHO STAT stalls or any other monitoring
of the "hung" transaction.

I want him to find out why they're hanging, he wants to know if Trace just
ignores this kind of "transaction".  He is not sure if there is even a 
begin time for this, but is going to check.

Thanks.

liz (it's been WAY too long since I worked with Trace!)

Do these transactions complete?  Or are they aborted???

If they are aborted for some reason they may not have an end logged by
ACMS, but I doubt it.

Do they span collection periods? (ie do they perform collections on the hour?
and these start and stop in different collection periods?)  If so they won't
get matched up.  They will need to specify longer collection intervals.

We don't "ignore" anything, I'm betting on the short collection window.

George

One way to check would be to compare starts with no ends to ends with no starts
in 2 adjacent collection periods...

Using EPID and other fields to match them up.

George

Thanks, George, that will help!