Re: Kinda urgent Connection error messages

From: Joe Weinstein (joeNOSPAM_at_bea.com)
Date: 11/02/04

  • Next message: Joe Weinstein: "Re: unknow exception from jdbc driver"
    Date: Mon, 01 Nov 2004 16:47:15 -0800
    
    

    jdnospam@hevanet.com wrote:

    > Joe,
    > There are a ton of locks in SQL Server under Locks/Process ID that
    > reference the web renewal update table, but we know no one is using it.

    Are you doing XA transactions? If so, in-doubt transactions may be holding
    locks. Your DBA should be able to associate the locks with the connection
    that holds them. Are you managing transactions yourself or are they managed
    by websphere?
        You may have to cycle websphere to truly kill all the connections it's
    made. If that doesn't clear it I'll be surprised, and you might have to cycle
    the DBMS. I can tell you that nothing you've shown implicates the driver at
    all. If you were using WebLogic, I'd have lots of tools to help you...

    > Most of the properties of these locks show this:
    > sp_executesql;1

    That implies use of PreparedStatements.
    >
    > or this:
    > BeginTrans

    That sounds like maybe bad application code. How are these transactions started?
    You should never be sending "BEGIN TRAN" SQL. You should be only using setAutoCommit()
    and commit()/rollback() JDBC calls.

    >
    > So you are probably right, but I don't know where to look for/which error log. Do I use Enterprise Manager or get on the SQL Server box and look at Win 2000 error log?
    >
    > What would you do to clean up these locks?

    As above. First thing is to cycle the client (websphere).

    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: Joe Weinstein: "Re: unknow exception from jdbc driver"

    Relevant Pages

    • Re: Transaction Deadlocks your thoughts?
      ... In #1 I have quite a few long transactions which are unavoidable, ... > locks, the more likely it is that you will bump into someone in this bad ... > Wayne Snyder, MCDBA, SQL Server MVP ... > community of SQL Server professionals. ...
      (microsoft.public.sqlserver.programming)
    • Re: row vs page locking...
      ... so they automatically escalate to page level locks. ... 'Lock Escalation' - see Books Online. ... SQL Server 2005 is going to have a Snapshot ... Good old fashioned locking is less sexy, but I find, more productive! ...
      (microsoft.public.sqlserver.server)
    • Re: Repeatable read. What is it exactly...
      ... SQL Server will hold locks on the data you have read ... can change change the data until you commit or rollback. ... SQL Server locks the data you read. ... > as transaction Isolation levels go. ...
      (microsoft.public.sqlserver.server)
    • Re: Locking in SQL Server and Oracle
      ... I am glad you would like to stay with SQL Server :-) ... > hard it would be to convert to Oracle during our next PeopleSoft upgrade. ... > had thought that since databases are databases, tables are tables, and SQL ... > uses row-level locks exclusively. ...
      (microsoft.public.sqlserver.server)
    • Re: Database Blocking Redux
      ... SQL Server stores rows on pages and pages on extents. ... Given the number of locks to manage, it's rare for SQL Server to lock individual rows. ... If SQL Server finds there are too many pages locked, it escalates locks to the entire extent and then to the entire table. ... When reading rows using SqlDataReader, does reading the next row release the lock on the previous row? ...
      (microsoft.public.dotnet.framework.adonet)

    Loading