• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
identifying MS SQL Server deadlock exceptions?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

identifying MS SQL Server deadlock exceptions?


  • Subject: identifying MS SQL Server deadlock exceptions?
  • From: email@hidden
  • Date: Tue, 21 Oct 2003 12:12:38 CDT
  • Priority: 3 (Normal)

[demime could not interpret encoding binary - treating as plain text]
In my exception logs, I'm seeing exceptions logged like:

JDBCAdaptorException:
EvaluateExpression failed: <com.webobjects.jdbcadaptor.JDBCExpression:
"UPDATE EO_PK_TABLE SET PK = 12109 WHERE NAME='CBPublicationtext'">: Next
exception:SQL State:40001 -- error code: 1205 -- msg: Your transaction
(process ID #85) was deadlocked with another process and has been chosen
as the deadlock victim. Rerun your transaction.


Fair enough; I know how to recover from this; just call saveChanges() again.

But I'm not sure how to identify these exceptions in code, since all I
have is a textual summary of the exception. Does anyone know what the
charecteristic properties of this JDBCAdaptorException are, indicating
deadlock?  It might vary depending on db; I'm talking MS SQL Server 7.
There are so many keypaths that one can follow from a
JDBCAdaptorException, I'm not sure which one will reveal what property to
indicate this deadlock exception.

--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: 404, 505 and Apache
  • Next by Date: Re: mandatory relatoinship preventing deletion?
  • Previous by thread: Re: download through Hyperlink
  • Next by thread: Re: optimistic locking recovery
  • Index(es):
    • Date
    • Thread