Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Deadlock Expand / Collapse
Author
Message
Posted Thursday, April 18, 2013 6:56 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, May 2, 2013 9:54 PM
Points: 24, Visits: 88
One of the system in my company was not available on the 9th Apr. As the application team in my company check in the log.. they found this error

2013/04/09 15:39:05:391 ERRORservices.ib101_access.register.IBRegisterSecurityImageServices: Error details :org.hibernate.exception.SQLGrammarException: could not insert:[net.penril.ibss.core.hibernate.IbUser]
Caused by:com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded.

2013/04/09 15:39:17:559 ERRORenterprise.services.ib101_access.IBGenericLoginServices: Error details :org.hibernate.exception.SQLGrammarException: could not update:[net.penril.ibss.core.hibernate.IbCustProfile#4737
Caused by:com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded.

2013/04/09 15:39:43:487 ERRORenterprise.services.ib101_access.IBGenericLoginServices: Error details :org.hibernate.exception.SQLGrammarException: could not update:[net.penril.ibss.core.hibernate.IbCustProfile#2951]
Caused by:com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded

its suspected because of deadlock. But i have no idea where to check on this issue. Im very new in this. Please help.

Post #1444202
Posted Friday, April 19, 2013 2:09 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:51 PM
Points: 42,756, Visits: 35,850
Lock request timeout will not be caused by a deadlock.

You can look in the system health extended events session to see if you have had any deadlocks, but I suspect you should be directing your investigation elsewhere.
http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/12/13/an-xevent-a-day-13-of-31-the-system-health-session.aspx



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1444264
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse