Logout takes 20 minutes?

I have a problem where our middle tier and all clients connected to it stops
responding for 5 to 20 minutes once or twice a day.
I now did a Profiler trace and saw that there is an Audit Logout entry with
the following data:
EventClass:Audit Logout
CPU:3641
Reads:203866
Writes:0
Duration:1272060
Can anybody tell my why this sometimes take so long, and how to stop it?
Thanx,
ErrolThe logout event duration is the amount of time the user was logged in and
is not directly related to your problem.
Check for rpc completed and batch completed events for exceptionally long
durations. The symptoms you describe may be related to blocking so check
for blocked processing using sp_who2.
Hope this helps.
Dan Guzman
SQL Server MVP
"Errol Terblanche" <Errol Terblanche@.discussions.microsoft.com> wrote in
message news:54DCBF8F-DBFC-41D5-9062-78D64DA01799@.microsoft.com...
>I have a problem where our middle tier and all clients connected to it
>stops
> responding for 5 to 20 minutes once or twice a day.
> I now did a Profiler trace and saw that there is an Audit Logout entry
> with
> the following data:
> EventClass:Audit Logout
> CPU:3641
> Reads:203866
> Writes:0
> Duration:1272060
> Can anybody tell my why this sometimes take so long, and how to stop it?
> Thanx,
> Errol
>|||Also check for any processes that are in rollback state. You might have
uncommitted transactions that are rolling back.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:Ou9V1enwEHA.1192@.tk2msftngp13.phx.gbl...
> The logout event duration is the amount of time the user was logged in and
> is not directly related to your problem.
> Check for rpc completed and batch completed events for exceptionally long
> durations. The symptoms you describe may be related to blocking so check
> for blocked processing using sp_who2.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Errol Terblanche" <Errol Terblanche@.discussions.microsoft.com> wrote in
> message news:54DCBF8F-DBFC-41D5-9062-78D64DA01799@.microsoft.com...
>|||I have looked for blocks in the Process Info window, but there where none.
I will get a more complete trace to see if i can see anything else.
There are no Batches that took more that 170ms.
I'm starting to think it might be ADO as the middle tier sets up the
connection but it hangs at the connection.connect statement. When this
happens all users that connect gets a connection assigned to them but they
all hang at the connection.connect statement. The connection is set up to
timeout after 15 seconds, but this doesn't happen so i don't think it is
truely a connection problem. After some time all the pending connections
suddenly open, practically all at once.
I have also set up a second middle tier connecting to the same database and
it runs fine and connects promptly even when the first middle tier is
hanging...
Any advice?
Thanx,
Errol
"Mike Epprecht (SQL MVP)" wrote:

> Also check for any processes that are in rollback state. You might have
> uncommitted transactions that are rolling back.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:Ou9V1enwEHA.1192@.tk2msftngp13.phx.gbl...
>
>