Re: Ecommerce account is logged in for a long time on SQL Server
From: Joe Weinstein (joeNOSPAM_at_bea.com)
Date: 11/15/04
- Next message: yuvalz: "RE: Tomcat, struts and SQL Server"
- Previous message: Joe Weinstein: "Re: Ecommerce account is logged in for a long time on SQL Server"
- In reply to: jdnospam_at_hevanet.com: "Ecommerce account is logged in for a long time on SQL Server"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Nov 2004 09:44:49 -0800
jdnospam@hevanet.com wrote:
> I'm monitoring our SQL Server over the weekend to see what is happening
> with the Ecomm login account that allows nurses to renew licenses online.
> Using the standard trace template which has 2 events, "Audit Login" and
>"Audit Logout", I find that the average over the weekend for anything over 10 minutes is 70 minutes!
>
> SELECT AVG(Duration / 60000) AS AverageOfMinutesLoggedIn
> FROM AllNightStandardProfileForEcomm
> WHERE (Duration / 60000 > 10)
>
> Scratching my head here. Does that mean that the webserver (ecomm account
>using java and MS JDBC driver) logs in and stays logged in until the nurse
>is done? Is this done at the start of a sesssion? Does this make sense? In
> ADO connections you login, do the dirty deed, and then log out. Over and
>over. I'm thinking that the web people wrote the code to login at session
>start and logout at session end. Is that correct? I'm thinking no.
>
> It does take a while for a nurse to renew her license(s) because they have
>to put in all sorts of continuing education credits. One nurse took 265 minutes!
> And her session was logged in to the database the whole time.
>
> Any ideas, insites?
Hi. If the JDBC client is middleware, it may be pooling connections, which is a good thing.
However, if it's a simple client, then it may keep a connection for as long as it needs,
and if it's really poorly designed, it may start a transaction to do what the nurse wants,
and then hold the connection open and do updates as the nurse does, locking data till (s)he
finishes... Maybe the application could get a connection at the start to verify the DBMS
is up, then close it and collect all the data while *not* connected to the DBMS. Then,
when it's ready to submit, re-open the connection and do the update is one quick move.
Joe Weinstein at BEA
>
> John
>
> **********************************************************************
> Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
- Next message: yuvalz: "RE: Tomcat, struts and SQL Server"
- Previous message: Joe Weinstein: "Re: Ecommerce account is logged in for a long time on SQL Server"
- In reply to: jdnospam_at_hevanet.com: "Ecommerce account is logged in for a long time on SQL Server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|